Start a project
Why Lisive Apps Technical Docs Support Hire us Shopify App Store

How it works, in detail.

For developers and technical leads evaluating Lisive: where our code runs in Shopify, how each app does its job, and the rules we build against.

01 · Buyer reaches checkout

Subtotal$184.00
Cart weight2.4 kg
Ship toHanoi, VN
POST /carrier/rates

02 · Lisive evaluates the cart

Heavy freight over 20 kgno match
Free shipping over $150matched
cart_total ≥ 150.00
country = VN
200 in 41 ms

03 · Checkout shows the right rates

Free shipping4–6 business days$0.00
Express1–2 business days$18.00
A checkout rate request, end to end. Rulify answers in-line; if it cannot, Shopify falls back to the store's own rates.
On the Shopify App StoreRulify, Vietnam Address Assistant and Order Editing & Swap are live today; eInvoice is in review.
In the checkout pathRate logic answers Shopify's request in-line.
Shopify FunctionsDelivery rules compiled to WebAssembly, run by Shopify.
Compliance-firstVietnamese e-invoices and the 2025 address model, built around the official rules.

01Apps

Three live apps, one in review. Each does one job.

Every unused setting is surface area that can fail while an order is being placed. Each of these apps does one job, and there is no second menu sitting behind it.

RulifyShipping & delivery logic, global

Shipping that charges what your policy actually says.

Problem
Shopify's built-in rates cover simple weight and price conditions. The real policy lives in someone's head, and the store loses margin every time it is applied wrong.
Approach
Conditions compose into scenarios, evaluated in priority order the moment Shopify asks for rates. Delivery options are hidden, renamed and reordered by a Shopify Function. No theme edits, no code.
Outcome
The rate a buyer sees is the rate you meant to charge, and you can see which scenario produced it.
  • Cart value
  • Weight
  • Destination zones
  • Product & customer tags
  • Tiered rates
  • Surcharges
Install Rulify
Demowalkthrough
ScenarioEnabled

Free shipping over $150

WHENCart totalis at least$150.00
ANDDestinationis in zoneVietnam North
THENRateFree“Free shipping”
Debug loglast 24 h
#1042Free shipping over $150matched41 ms
#1041Heavy freight over 20 kgmatched36 ms
#1040No scenario matchedno match29 ms
Order #1042Issued
Serial1234567890 Number0000431 Issued12:04:19 +07 BuyerExample Trading Co Ltd Tax code0101245789
Total incl. VAT4,620,000 VND
Invoice queuetoday
#1041Auto-issued on paymentissued2s
#1040Buyer declined VAT invoiceskippedn/a
#1039Provider rejected tax codefailedretry

eInvoiceE-invoice automation for Vietnam In review

Tax invoices, issued the moment an order is paid.

Why
Vietnamese law requires an e-invoice per sale. Most stores issue them by hand in a provider portal, then reconcile against Shopify at month end.
What it does
eInvoice listens for paid or fulfilled orders, issues through your provider and writes the serial and number back onto the order. An order cannot be invoiced twice.
  • Auto on paid / fulfilled
  • Manual issue
  • Storefront VAT request
  • Idempotent by order
  • Reason on every failure

In review on the Shopify App Store. Installable soon.

Vietnam Address AssistantAddress normalization

Addresses that still match the map after the provinces changed.

Change
On 1 July 2025 Vietnam removed the district tier. 63 provinces became 34 and 10,035 communes became 3,321, on the same morning.
Approach
A block on the Thank you page shows province, ward and a delivery note, pre-filled by a resolver that handles legacy pairs and misspellings. The buyer presses Confirm.
Outcome
Three custom attributes your carrier can read. The checkout address is left alone. The app is free.
  • 34 provinces
  • 3,321 communes and wards
  • Buyer-confirmed
  • Thank you page
  • Free
Install Vietnam Address Assistant
Thank you pageConfirmed
Province79:Ho Chi Minh City Ward26737:Ben Thanh Ward NoteDeliver during office hours
Shipping address at checkoutunchanged
Resolver63 → 34
inputP. Ben Nghe, Q.1, TP.HCMmatchedlegacy
inputXa Cam Giag (typo)matchedfuzzy
inputProvince not recognisedbuyer picksmanual
Order #1048 · editConfirmed
VariantSize M / Black → Size L / Black Pricesame price AddressStreet and ward updated Countrylocked
Fulfillment holdreleased in 30 min
RuleEnabled

Allow edits for 30 minutes and hold fulfillment

WHENOrder ageis less than30 min
AND NOTPayment gatewaycontainsCOD
THENAllowaddress, variant1 edit · hold 30 min
Editstoday
#1048Variant changed by customerapplied1/1
#1047Shipping address correctedapplied1/1
#1046Edit window closedlocked30 min

Order Editing & SwapCustomer self-service edits

Let customers fix their own order, before it ships.

Problem
A wrong size or a typo in the address turns into a support email, a manual edit in admin, and sometimes a parcel sent to the wrong place.
Approach
From the Thank you page or the order in customer accounts, customers swap to an in-stock variant at the same price or correct the shipping address within the same country. Allow and deny rules decide which orders qualify, using order age, payment gateway, fulfillment and financial status, order total, destination and more.
Outcome
The order is held from fulfillment while edits are allowed, then released on time. Every edit is logged with before and after values, and you can be emailed when one happens.
  • Variant swap
  • Address edit
  • Allow & deny rules
  • Edit window & limit
  • Fulfillment hold
  • Rule templates
  • 7 languages
  • 20 edited orders included
Install Order Editing & Swap

02Engineering principles

What we mean when we say done.

These are the rules every app is built against.

  1. Principle 01

    What happens on the day we are the thing that is broken.

    A valid request with no matching scenario returns an empty rate list, unless the merchant has set a safety fallback rate. Technical failures return an HTTP error so Shopify can use the store's backup rates.

  2. Principle 02

    Operations are idempotent.

    Every invoice is keyed to its order. Duplicate webhooks, retries and a merchant clicking twice all converge on one legal document instead of three.

  3. Principle 03

    If an operation is skipped or fails, it gets written down.

    The reason is recorded next to the order it belongs to. Failures stay visible in the queue instead of being retried away in the background.

  4. Principle 04

    The smallest dataset we can get the job done with.

    No customer data beyond what a document legally requires. Provider credentials are encrypted at rest. Deletion requests actually delete.

03Start

Got a harder version of this?

Tell us which Shopify constraint or system you're up against. You'll hear back from an engineer, not a sales queue.

Hire Lisive hello@lisive.com