Skip to content
Brickhouse.
All integrations Integration / Daily Orders

NDIS invoice checkout.

Daily Orders is a registered NDIS provider, and its planners are bought as assistive technology by people who are not the ones paying for them. The NDIS checkout takes the same cart as every other customer and ends in an invoice instead of a payment.

Store case study
  1. 01

    Shopify

    The catalogue and the cart, read through the Storefront API. Both checkouts start from the same cart.

  2. 02

    Angular storefront

    The NDIS checkout itself: a three-step form rendered inside the headless app.

  3. 03

    NDIS order service

    A dedicated service on Vercel that receives the request and returns the invoice as a PDF.

  4. 04

    Storyblok

    The heading and introduction on the NDIS checkout, so the team can edit the wording.

  5. 05

    Klaviyo

    Records the NDIS checkout against the customer, with the items they were invoiced for.

The objective

What it
had to do.

A Shopify checkout ends in a payment. An NDIS purchase does not: the invoice is settled afterwards by the participant, their plan manager or the NDIA, and the person placing the order is often an occupational therapist or support worker rather than the participant it is for.

Business objectives

  • Let an NDIS participant order from the same catalogue, product pages and cart as every other customer, rather than a separate store or an emailed quote
  • Issue an invoice without taking payment, in a form that self managed, plan managed and NDIA managed participants can each claim against
  • Keep the person placing the order separate from the participant, so an OT or support worker can order on someone else’s behalf and still receive the order updates
  • Collect the NDIS number and the required declarations before the invoice is issued, not after

The stack

  • Shopify Storefront API
  • Angular
  • Vercel
  • Storyblok
  • Klaviyo
  • Google Tag Manager

Key flows

How it runs.

3 flows

Flow 01

From cart to invoice request

The NDIS path opens from the cart, beside the ordinary checkout, and collects what an invoice needs in three steps.

  1. 01 Storefront

    The cart offers “Invoice for NDIS” alongside the normal checkout link.

  2. 02 Shopify

    The cart lines are read from the Storefront API and shown back as the quoted items.

  3. 03 Storefront

    The person placing the order enters their own name, email and phone. They are the one who receives the confirmation, shipping and tracking emails.

  4. 04 Storefront

    Participant details follow: name, NDIS number, phone and delivery address, with an optional authority to leave.

  5. 05 Storefront

    Three declarations are ticked before the request can be sent: the site terms, compliance with NDIS legislation, and responsibility for eligibility.

Flow 02

An invoice instead of a payment

Submitting the form creates the invoice. No card is asked for at any point.

  1. 01 Order service

    The cart, the contact and the participant details arrive in a single request.

  2. 02 Order service

    The invoice comes back as a PDF and downloads in the browser straight away.

  3. 03 Storefront

    A confirmation tells the customer a copy has gone to the email address they gave.

  4. 04 Shopify

    The cart is cleared, so the same items are not ordered twice.

  5. 05 Klaviyo

    An NDIS checkout event is recorded against the customer, with the line items.

Flow 03

One invoice, three payers

The form does not ask how a plan is managed. The same invoice works for all three funding types; only where it goes next is different.

  1. 01 Self managed

    The participant claims the invoice through their own portal.

  2. 02 Plan managed

    The participant forwards the invoice to their plan manager.

  3. 03 NDIA managed

    The participant emails the invoice to Daily Orders with their date of birth and chosen budget.

More integrations.

All integrations

Warranbrooke

  • Shopify
  • Integration service
  • Cin7 Core
  • Postgres
  • Resend

Quotes and Cin7 price books

Carts that should be quoted are raised as draft quotes in Cin7 Core, and Cin7 price tiers are written into Shopify price lists.

View integration →

EDMO Asia Pacific

  • Shopify
  • Integration service
  • Cin7 Core
  • Postgres
  • Resend

POA quotes and Cin7 price books

Priced lines go through checkout, price-on-application lines become a draft quote in Cin7 Core, and Cin7 price tiers are written into Shopify price lists.

View integration →

Wilding Foods

  • Shopify
  • Plutocracy shipping app
  • Be Cool API
  • AWS
  • PostgreSQL

Shopify to Be Cool couriers

Delivery windows in the cart, bulk bookings with Be Cool Refrigerated Couriers, box labels and tracking written back to the Shopify order.

View integration →

Your systems, connected

What does your
store not talk to?

Tell us which systems you run and where the re-keying happens. We’ll come back within one business day with where we would start.

Start a project