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 sandboxView 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 and you want full control over each document, start with the JavaScript SDK or direct API. If you would rather hand orders over and let invoicing follow automatically, connect the store as an order integration: Shopify, WooCommerce, or any custom store.

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 issuerMerchant entity
Order referenceStore in metadata
Refund pathCredit note
Order Integrations

Connect a store once, invoice every order

Order integrations take care of the timing, emails, fiscalization, and refunds for you. A custom store gets the same automation as the built-in connectors: give your shop the webhook URL and signing secret, and send each order and its status changes as they happen.

Shopify

Authorize the store; order webhooks are registered for you.

WooCommerce

Native wc-auth approval, no plugin; webhooks are managed for you.

Custom store

Your own shop sends each order as a signed webhook or through the API.

How Orders Are Handled
New connections start with automatic processing on: paid orders are invoiced as they arrive, pending online payments wait until paid, and unpaid bank transfers start as estimates
Send the order again when it is paid, shipped, cancelled, or refunded; the same order ID updates it
A full refund voids the invoice with a credit note; cancelled orders never create new documents
Fiscalization, invoice email, payment recording, and SKU catalog linking follow the connection settings
Connect a custom storeWooCommerce guide
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.

01

Create one sandbox entity for a test store or merchant

02

Turn one order into one invoice

03

Render the PDF and inspect totals, numbering, and branding

04

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 integrationsSee 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 sandboxSee platform architecture