Use Case: E-Commerce

Turn orders into invoices without improvising the hard parts

The first real design decision is when an order becomes an invoice. Space Invoices helps once you know your trigger: order, payment, or fulfillment. It also gives you the right downstream path for refunds and document delivery.

Start free sandbox View e-commerce docs

Who This Is For

You already have order or payment events and need invoices to follow them automatically

You need a clean order-to-invoice and refund-to-credit-note workflow

You sell across borders and do not want to encode tax logic per market yourself

Not A Fit

You only need manual one-off invoicing

You have not decided when invoices should be issued

You expect checkout tooling rather than invoicing infrastructure

Recommended Path

Keep issuance logic on your backend

If your store already emits order and payment events, start with the JavaScript SDK or direct API. If you use supported order integration flows such as Shopify authorization, validate the current connector behavior in docs before designing around it.

Issue on event

Create documents from order, payment, or fulfillment milestones.

Credit notes for refunds

Keep finalized invoices immutable and reverse correctly.

Entity Model

One store or legal merchant per entity

If one merchant identity issues the invoices, keep it in one entity. If your brands, countries, or legal sellers differ, split them into separate entities so numbering, branding, and compliance stay clean.

Invoice issuer Merchant entity

Order reference Store in metadata

Refund path Credit note

First Sandbox Milestone

Prove one order and one refund

Before rollout, validate a single store in sandbox end to end. The key is not just creating one invoice, but proving the timing and reversal logic.

Create one sandbox entity for a test store or merchant

Turn one order into one invoice

Render the PDF and inspect totals, numbering, and branding

Test one refund path and confirm it creates a credit note, not an invoice mutation

Operational Gotchas

Decide whether to issue on order creation, payment confirmation, or fulfillment before coding

Store order IDs in metadata for support and reconciliation

Keep per-store entities when legal merchant identity, currency, or branding differs

Compliance Notes

Seller country and buyer location both influence tax behavior. EU B2B orders may require reverse-charge handling and VIES validation.

Sandbox is the right place to validate order timing, cross-border taxes, and refund behavior before you send real invoices or customer emails.

Inspect order integrations See refund document flows

Start with one workflow, not a whole rewrite

Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.

Start free sandbox See platform architecture