Inventory & orders

Inventory and orders are the operational heart of commerce. This guide explains inventory modes, the order lifecycle, fulfillment, and refunds so stock stays accurate and customers get timely updates.

Inventory modes

Tracked SKUs decrement on purchase; unlimited SKUs skip stock checks — useful for digital goods or made-to-order items with separate capacity planning. Oversell protection can reserve inventory at checkout start on high-demand drops so two shoppers do not buy the last unit.

Multi-location inventory (when enabled) assigns stock to warehouses or stores. Routing rules decide which location fulfills. Keep location names understandable to operators (“EU-West” not “loc_7”).

1. Mark each SKU tracked or unlimited deliberately.
2. Set low-stock thresholds and notify merchandising.
3. For drops, enable reservation windows that match your checkout timeout.
4. Reconcile physical counts on a schedule; the system is only as good as the last cycle count.

Order lifecycle

Orders move through pending paid fulfilled closed (with exceptions for canceled, refunded, and disputed). Each transition can emit webhooks for your ERP or fulfillment partner.

Pending covers checkout started or payment authorization in flight. Paid means funds captured or authorized per your payment settings. Fulfilled means items have shipped or been delivered digitally. Closed is the terminal happy state after returns windows lapse per your policy.

pending → paid → partially_fulfilled → fulfilled → closed
         ↘ canceled
         ↘ refunded (full or partial)

Train support on which states allow which actions. Capturing payment before stock confirmation is a business choice — document it.

Fulfillment

Partial fulfillments are supported when items ship separately. Attach tracking numbers so customers receive shipment notifications automatically. Digital goods should deliver download or license entitlements as part of the paid transition.

• Print packing slips from the order detail or export batches.
• Use consistent carrier codes so tracking links resolve.
• Notify customers when fulfillment is delayed before they open tickets.

Integrations: push paid orders to 3PLs via webhooks or API. Make handlers idempotent using order IDs so retries do not create duplicate shipments.

Refunds

Refunds restock inventory when configured. Document your return window on the storefront so support and automation stay aligned. Partial refunds should itemize what was refunded for finance.

Chargebacks follow provider processes — respond with fulfillment proof and customer communication logs. Keep evidence exportable from the order record.

• Low-stock alerts reach a human mailbox
• Fulfillment SLA defined and monitored
• Tracking emails verified in production
• Refund restock behavior matches policy pages

Troubleshooting

Negative stock: check oversell settings, manual adjustments, and channel sync delays.

Webhook storms: dedupe on event ID; do not create shipments twice.

Customer says shipped but no tracking: carrier code or number malformed — validate before send.

Prerequisites & preparation

Before changing production settings for inventory and orders, align the people who own content, DNS, analytics, and approvals. A fifteen-minute kickoff that names owners prevents multi-day Slack archaeology later. Capture decisions in the workspace notes so the next teammate inherits context instead of guesswork.

Gather credentials and access: workspace admin or editor role, DNS control when hostnames are involved, payment or API sandbox accounts when money paths are involved, and a shared checklist link. Confirm which environment you will rehearse in — preview first, production only after a green run.

Define tracked vs unlimited SKUs, fulfillment SLAs, and refund/restock policy aligned to storefront copy.

Detailed walkthrough

Work the happy path slowly the first time. Narrate what you expect to see after each click: a status badge, a DNS record, a webhook delivery, a Lighthouse metric. When reality diverges, stop and resolve the mismatch instead of clicking ahead — most outages begin as ignored yellow states.

1. Configure inventory modes and low-stock alerts to a monitored inbox.
2. Walk an order through pending paid fulfilled in staging.
3. Attach tracking on a partial fulfillment and verify customer messaging.
4. Refund with and without restock; confirm resulting quantities.
5. Enable webhooks to ERP/3PL with idempotent handlers.

Edge cases & failure modes

Plan for partial failure. Networks drop, registrars delay, providers rate-limit, and humans approve the wrong revision. Your runbook should say what “abort” looks like: leave preview up, roll back the release, or freeze campaigns until metrics recover.

• Sandbox and live keys crossed between environments.
• Tax inclusive labels disagreeing with checkout math.
• Webhooks delivered twice without idempotent handlers.

QA checklist before you announce

• Happy path verified on mobile and desktop
• Failure path messaging reviewed
• Owners named for the first hour after launch
• Rollback or freeze path documented

Operating the change

After launch, watch the metrics that prove the change worked — not vanity charts. Pair quantitative signals with one qualitative check (support ticket themes, sales feedback). Schedule a follow-up within a week to remove temporary flags, raise DNS TTLs, or archive the experiment.

Cycle-count on a schedule; reconcile channel stock before peak season.

Unlimited inventory still needs operational capacity — alert when order volume exceeds staffing.

Teach support which states allow capture, fulfill, cancel, and refund to avoid conflicting actions.

Partial fulfillments should keep customers informed item-by-item with valid carrier codes.

Chargeback evidence is easier when fulfillment proof lives on the order record from day one.

Reservation windows on drops should match checkout timeouts to avoid ghost holds.

Multi-location routing names should be human-readable for operators under pressure.