E-commerce
April 8, 2026
E-commerce order management covers everything that happens after the “pay” click (or B2B equivalent) until the transaction is fully closed: validation, stock allocation, routing to warehouse or store, shipping, invoicing, exception handling, returns, and refunds. We often refer to an OMS (order management system) when a dedicated system orchestrates these steps beyond the store’s basic admin screen.
This Operations guide lays out the concepts, typical statuses, edge cases, and integrations. It extends the e-commerce product catalog (SKUs, lines, attributes): clean catalog data limits downstream order errors. For the upstream funnel (design, checkout, store features), refer back to the blog’s dedicated guides.
Good order management reduces picking errors, overselling, and support workload: it aligns marketing promises with operational reality.
Qstomy operates downstream on customer questions (“where is my order?”, “can I change the address?”) when your statuses and policies are clearly documented.
Product and supply teams take part in trade-offs: a stock availability promise on a product page without real inventory behind it causes cancellations and customer service workload to skyrocket.
Executives must connect gross margin with the processing cost of an order: hidden costs of re-entry, support calls, and returns can exceed visible logistics costs.
In the field, order management is also experienced as a chain of responsibility: who approves an exceptional discount, who authorizes a free reshipment, who decides when the carrier and warehouse pass the buck. Without written procedures, each agent applies a different interpretation and customers receive contradictory responses on social media.
Seasonal peaks are not just a volume problem: they reveal bottlenecks (label printing queue, API limit, weekend staffing) that must be sized in advance with realistic load scenarios.
Finally, master data quality (customer record, standardized address, product reference) is the OMS’s silent fuel: investing in data cleanliness at capture time avoids hours of downstream reprocessing.
Summary
Definition: OMS, store and warehouse
The e-commerce platform creates an order record with lines, prices, taxes, and customer. The OMS often goes further: multi-site allocation rules, cross-channel orchestration, synchronization with ERP and WMS. Some SMBs manage everything in the store admin until a volume where a separate OMS becomes relevant.
OMS vs WMS
The OMS decides what to fulfill and where to draw stock from; the WMS optimizes how things are done in the warehouse (locations, picking). The boundaries can blur when the vendor offers an integrated suite.
Order as an event
Each status transition can trigger actions: email, warehouse task, accounting entry: see e-commerce automation.
Source of truth
Avoid three Excel files and the store as competing repositories: designate which system holds the “official” order for customer service.
Idempotency
Webhooks or marketplace order imports must not duplicate the same order if the message is replayed.
Scalability
Moving from a few orders per day to thousands requires queues, idempotency, and monitoring: plan ahead before the first seasonal peak.
Team training
Tools are only as good as operators sharing the same definition of “shipped” or “in dispute.”
Single cockpit
Even if several tools coexist, giving operations teams an aggregated view or a single case number brings peace of mind.
Lifecycle: statuses, transitions, and customer visibility
Common statuses include pending payment, paid, being prepared, shipped, delivered, canceled, refunded. Exact labels vary; what matters is the shared semantics across teams and integrations.
Fraud review queue
Some orders remain "under review" before acceptance: the customer should see an honest message without revealing internal criteria.
Partial preparation
Intermediate states when only part of the line items is ready: customer communication must avoid ambiguity.
History
Change log (address, manual discount): essential for disputes and compliance.
Notifications
Each meaningful change should trigger the expected email or SMS: an omission generates support calls.
Internal SLAs
Define the maximum delay between accepted payment and moving to preparation: a shared objective for ops and marketing.
Partial visibility
The customer should not see obscure internal codes: translate statuses into understandable labels.
Archiving and proof
Keep the order state at the time of sale (price, taxes, promotional terms) to defend a dispute one year later: timestamped snapshots or exports.
Test orders
Isolate QA orders so they do not pollute stats or trigger real shipment: dedicated accounts and flags.
Order merging
When a customer places two successive orders, consolidating before shipment can reduce shipping costs if your rules allow it and if stock permits.
Available stock, reservation, and customer promise
The ATP (available to promise) connects physical inventory, reservations, replenishment lead times, and competing channels. A rule that is too aggressive creates overselling; too conservative, phantom stockouts.
Soft vs hard allocation
Reserve at payment or only when picking starts: a trade-off between experience and cancellation risk.
Pre-order
Collecting payment before physical stock requires careful management of promised dates and delay communications.
Store stock vs web
Priority rules if the same SKU is sold online and at checkout: without a clear OMS, inventory discrepancies explode.
Synchronization
Batch delay versus real time: to be documented for merchandising and SEO of “in stock” pages.
Alert thresholds
Notify purchasing and merchandising when stock coverage drops below X days of sales for a key SKU.
Cycle counts
Physically reconcile part of the references to reduce drift between systems.
Multi-country coverage
The same SKU can be supplied from multiple hubs: the OMS chooses the source based on customer lead time, cost, and availability, not only geographic distance down to the nearest kilometer.
Seasonal products
Legal sales dates or limited collections: automatically disable non-sellable lines after a date to avoid orders that cannot be fulfilled.
Omnichannel: web, store, marketplaces and partners
Orders can come from the website, apps, marketplaces, and EDI resellers. Each channel imposes different formats, SLAs, and sometimes fees. See marketplace vs store.
Intelligent routing
Choose the warehouse or store that minimizes lead time or transport cost while respecting stock constraints.
Ship-from-store
Sellers prepare orders from the store: training and mobile picking tools are required.
In-store pickup
“Ready for pickup” notification and holding times: specific statuses in the OMS.
Priority conflicts
If two channels claim the last unit, the business rule must be coded and audited.
Channel pricing
Marketplace commissions change net margin per order: the same SKU may require different stock-priority logic.
Cross-network click & collect
Franchised store networks: who owns the stock displayed online for pickup?
Social networks and live selling
Sales from live shopping or messaging platforms must materialize as traceable orders in the same system of record to avoid double stock and missed invoicing.
Subscriptions
Automatic renewals: a recurring order is not identical to a one-time purchase; statuses and recurring billing must be defined.
Donations and solidarity D2C
Amounts transferred, proof: specific line items for accounting and external communication.
Split shipping and multiple deliveries
An order can generate multiple shipments (different stock locations, heavy products, mixed pre-order). The customer must receive one tracking number per package and a clear view of what is still to come.
Billing
Invoice upon shipment or as a single order: accounting and VAT impact depending on the country.
Shipping costs
An unexpected split can cancel a “free shipping” promise: rules must be defined before marketing.
Communication
Avoid five identical emails: group notifications when relevant.
Partial returns
Refund only the returned line items in good condition: linked to customer service and warehouse.
Gift package
Ship one part in neutral packaging and another with branding: separate instructions per line item.
Environment
Consolidating shipments when the customer accepts a slight additional delay can reduce transport footprint.
Insurance and declared value
Packages with multiple values: declaring each shipment correctly avoids disputes in case of partial loss.
Cancellations, changes, credits and refunds
Before shipping, changing the address or an item may be possible; after shipping, it is often return then refund. The legal withdrawal periods in B2C govern part of the process: see returns.
Seller cancellation
Confirmed stockout after payment: compensation procedure and transparent communication.
Partial refund
Commercial gesture or pricing error: track authorization and the impact on accounting.
Payment disputes
Chargeback: retention of proof of delivery and compliance.
Marketing consistency
Stop cart or loyalty follow-ups when the order is canceled: avoid inconsistencies.
Credit notes and partial credit notes
Store credit versus refund to the payment method: impact on cash flow and loyalty.
Processing times
The timelines communicated to the customer for refunds must be met, or communication proactively updated.
Legal withdrawal
Distinguish eligible products and exceptions (custom-made items, perishable goods depending on the framework): different workflows in the OMS.
Commercial gesture
Voucher versus refund: impact on cash flow and purchase recurrence to be modeled.
B2B: quotes, approval, credit, and scheduled deliveries
Professional orders may go through quotes, managerial approval, credit limits, and scheduled weekly deliveries. The cycle is not like express B2C.
Contract pricing
Price grids by customer or contract: the OMS must apply the correct list without error.
Purchase order
Referencing buyer and seller item codes for accounting reconciliation.
Multiple deliveries
Recurring purchases or construction schedule: split statuses and invoices.
B2B customer portal
Tracking open orders, duplicating a standard order: features to be defined with the OMS.
Payment terms
Bank transfer at 30 days end of month: a validated order does not imply immediate collection: link with receivables collection.
Minimum order
Block or alert below a threshold to preserve logistics profitability.
E-procurement
Baskets guided by an approved buyer-side catalog: the OMS must respect authorized lists and block out-of-contract items.
Integrations: ERP, 3PL, carriers and marketplaces
The OMS exchanges with the ERP (invoices, accounting inventory), the WMS or 3PL (shipping statuses), and carriers (labels, tracking). APIs must handle retries, errors, and daily reconciliation.
Status mapping
“Shipped” on the carrier side does not mean “delivered”: do not confuse the two in the customer interface.
Tracking numbers
Surface them early in the store and support tools to reduce tickets.
Accounting entries
Sale date vs. shipping date: rules to validate with finance.
Project workload
Each new connector is a mini-project: documentation, load testing, rollback plan.
Customs and documents
For international orders, the order must include the correct HS codes and amounts: errors = blocked parcels.
Integration tests
Anonymized datasets to replay a typical day before going live.
Asynchronous queues
When a partner is slow, do not block the entire order: retry strategies and a dead-letter queue for manual intervention.
Observability
Structured logs by order ID to investigate quickly during multi-system incidents.
Exceptions: fraud, addresses, stockouts, and edge cases
Incomplete address, lost package, damaged item, picking error: the “happy path” is not enough. Exception queues and roles (level 1 / level 2) speed up processing.
Fraud queue
False positives: a protocol to unblock a legitimate customer without excessive delay.
Stockout during preparation
Offer substitution, delay, or partial cancellation with explicit agreement.
Customer data
Namesakes, duplicate accounts: identity resolution to attach the correct order.
Medical or social emergency
Rare cases requiring human escalation despite automation.
Chargebacks and evidence
Keep POD signature, delivery photo, or detailed tracking according to card network requirements.
VIP customer escalation
Rules for manual acceleration without breaking fairness with other customers.
Weather and force majeure
Storms, strikes: communicate realistic timelines and log decisions to respond to claims with verifiable facts.
Service continuity
Recovery plan if the main OMS is unavailable: buffer queue, read-only switch, or controlled manual entry to avoid losing critical orders during peak periods or supplier incidents. Document an on-call number and a decision channel to unblock cases stuck in the queue without multiplying unanswered internal emails.
Shopify: orders, locations and best practices
In the Shopify ecosystem, orders, shipping profiles, and inventory locations are managed in the admin. Specific features evolve: check the official documentation for your plan and apps. For an assistant aligned with the statuses shown to customers: Qstomy integration on Shopify.
Fulfillment
Assign preparation to the right location or logistics partner: consistency with e-commerce fulfillment services.
Tags and flows
Tag orders (VIP, supplier delay) for automations and reporting.
Draft orders
Orders created by the merchant: useful for B2B and phone; process to avoid duplicates.
Documentation
Shopify: orders (documentation) as an entry point.
Shopify Flow automations
Simple scenarios can tag or notify according to rules: the general principle of automation is covered earlier in this guide.
Scope limits
Very advanced needs (multi-rule allocation across ten warehouses) may require an external OMS or custom development.
Staff permissions
Limit who can refund or cancel from the admin: reduces errors and internal fraud.
Accounting exports
Formats expected by your accountant: validate early to close months without re-entry.
Indicators, data quality and governance
Measure preparation lead time, picking error rate, canceled orders, exception resolution time. Cross-reference with your analytics reports to link product issues and customer service.
Address quality
Validation at entry reduces carrier returns: direct impact on cost.
Reconciliation
Compare paid, shipped, and collected orders: detect discrepancies early.
Roles and traceability
Knowing who changed a status or granted a discount: internal compliance.
Qstomy and support
Automated responses do not replace up-to-date statuses: synchronize chatbot content and OMS.
Weekly dashboards
Short ops / support / marketing meeting on top cancellation and delay reasons for corrective actions.
Living documentation
Update procedures when a new marketplace or a new carrier joins the scope.
Relationship with sales
Sales objectives (volume, basket size) must remain compatible with preparation capacity: regular arbitration between departments.
FAQ, summary and sources
Do you need an OMS from day one? Not necessarily; however, as soon as multiple inventories or channels overlap, a clear model becomes essential.
Who is responsible for the “official” order? Designate one system and export rules for the other tools.
How can you reduce WISMO inquiries? Reliable statuses, notifications, and a conversational assistant aligned with reality.
Sources
Qstomy articles: catalog, automation, fulfillment, Shopify, returns, and chatbot (links in this guide).
In summary, e-commerce order management is the operational common thread between customer promise and physical execution: investing in clear statuses, robust integrations, and honest communication pays off more than simply stacking apps.
Additional reading
The product catalog (already linked in the introduction) upstream determines the quality of order lines: consistent SKUs, barcodes, and attributes prevent downstream errors.
In the short term, a shared procedures handbook between support, warehouse, and finance is often better than a poorly adopted new tool.
Enzo Garcia
April 8, 2026
