E-commerce
April 8, 2026
The 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 talk about 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 (SKU, lines, attributes): clean catalog data limits downstream order errors. For the upstream funnel (design, checkout, store features), refer to the dedicated blog guides.
Good order management reduces picking errors, overselling and support load: it aligns marketing promises and operational reality.
Qstomy comes into play downstream for customer questions (“where is my order?”, “can I change the address?”) when your statuses and policies are clearly documented.
The product and supply teams take part in trade-offs: promising availability on the product page without real stock behind it causes cancellations and increases customer service workload.
The executives must connect gross margin and the cost of processing an order: hidden costs from re-entry, support calls and returns can exceed the visible logistics cost.
On the ground, order management is also experienced as a chain of responsibilities: who approves an exceptional discount, who authorizes a free return, who decides when the carrier and warehouse pass the buck. Without written procedures, each agent applies a different interpretation and customers receive contradictory answers on social media.
The seasonal spikes are not just a volume problem: they reveal the bottlenecks (label printing queue, API limit, weekend staffing) that must be sized in advance with realistic load scenarios.
Finally, the master data quality (customer record, normalized address, product reference) is the silent fuel of the OMS: investing in clean data at capture avoids hours of downstream rework.
Summary
Definition: OMS, store and warehouse
The e-commerce platform creates an order record with line items, prices, taxes, and customer. The OMS often goes further: multi-site allocation rules, orchestration across channels, synchronization with ERP and WMS. Some SMEs handle 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 source stock; the WMS optimizes the how inside 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 sources of truth: designate which system holds the « official » order for customer service.
Idempotence
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, idempotence, and monitoring: anticipate before the first seasonal peak.
Team training
Tools are only worth it if operators share the same definition of « shipped » or « in dispute ».
Single cockpit
Even if several tools coexist, giving operations staff an aggregated view or a single case number brings peace of mind.
Lifecycle: statuses, transitions and customer visibility
Common statuses include awaiting payment, paid, preparing, shipped, delivered, canceled, refunded. Exact labels vary; what matters is the semantics shared between teams and integrations.
Fraud 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 should avoid ambiguity.
History
Change log (address, manual discount): essential for disputes and compliance.
Notifications
Each useful change should trigger the expected email or SMS: forgetting one creates support calls.
Internal SLAs
Define the maximum delay between payment accepted and moving to preparation: a shared goal for ops and marketing.
Partial visibility
The customer must not see obscure internal codes: translate statuses into understandable labels.
Archiving and evidence
Keep the order state at the time of sale (price, taxes, promotional terms) to defend a dispute a year later: snapshots or timestamped exports.
Test orders
Isolate QA orders so as not to pollute the stats or trigger real shipping: dedicated accounts and flags.
Order merging
When a customer places two successive orders, grouping them before shipping can reduce shipping costs if your rules allow it and the stock permits.
Available stock, reservation, and customer promise
The ATP (available to promise) connects physical inventory, reservations, replenishment lead times, and competing channels. An overly aggressive rule creates overselling; too cautious, phantom stockouts.
Soft vs hard allocation
Reserve at payment or only when picking starts: a trade-off between customer experience and cancellation risk.
Pre-order
Charging before physical stock requires careful management of promised dates and delay communications.
Store stock vs web
Priority rules when 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 the SEO of “in stock” pages.
Alert thresholds
Notify purchasing and merchandising when stock coverage falls below X days of sales for a key SKU.
Cycle counts
Physically reconcile part of the SKUs to reduce drift between systems.
Multi-country coverage
The same SKU can be replenished from several hubs: the OMS chooses the source according to customer lead time, cost, and availability, not just geographic distance down to the kilometer.
Seasonal products
Legal sale dates or limited collections: automatically disable non-sellable items after a date to avoid orders that cannot be fulfilled.
Omnichannel: web, store, marketplaces and partners
Orders can come from the website, apps, marketplaces, 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
Store associates prepare orders from the shop: training and mobile picking tools required.
In-store pickup
Notification “ready for pickup” and holding period: 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 the net margin per order: the same SKU may require a different stock-priority logic.
Click & collect cross-network
Franchise store networks: who holds the stock displayed online for pickup?
Social media and live selling
Sales from live shopping or messengers must be materialized as traceable orders in the same system of record to avoid duplicate inventory and missed invoicing.
Subscriptions
Automatic renewals: a recurring order is not identical to a one-off purchase: statuses and repeated invoicing must be defined.
Donations and solidarity D2C
Amounts paid out, proof: specific lines for accounting and external communication.
Split shipments and multiple deliveries
An order can generate several shipments (different stock, heavy products, mixed pre-order). The customer must receive tracking for each package and a clear view of what is still to come.
Billing
Billing upon shipment or a single order: accounting impact and VAT depending on the country.
Shipping fees
An unexpected split can cancel a promise of « free shipping »: rules to define before marketing.
Communication
Avoid five identical emails: group notifications when appropriate.
Partial returns
Only refund the items returned in good condition: link with customer service and warehouse.
Gift package
Ship part in plain packaging and another with branding: separate instructions by line.
Environment
Consolidating shipments when the customer accepts a slight additional delay can reduce transport footprint.
Insurance and declared value
Multi-value packages: declaring correctly for each shipment avoids disputes in case of partial loss.
Cancellations, modifications, credits, and refunds
Before shipment, changing the address or an item may be possible; after shipment, it is often a return then a 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
Goodwill gesture or pricing error: track authorization and the impact on accounting.
Payment disputes
Chargeback: keep 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 announced to the customer for a refund must be met, or communication proactively updated.
Legal withdrawal
Distinguish eligible products and exceptions (custom-made, perishable goods depending on the framework): different workflows in the OMS.
Goodwill gesture
Voucher versus refund: impact on cash flow and repeat purchasing to model.
B2B: quotes, approvals, credit, and scheduled deliveries
B2B orders may go through quotes, hierarchical approval, credit limit, and scheduled deliveries by week. The cycle does not resemble express B2C.
Contract prices
Price lists by customer or contract: the OMS must apply the correct list without error.
Purchase order
Mapping buyer and seller item references for accounting reconciliation.
Multi-deliveries
Recurring purchasing or construction site schedule: split statuses and invoices.
B2B customer portal
Tracking open orders, duplication of standard orders: features to define with the OMS.
Payment terms
Bank transfer at 30 days end of month: the validated order does not imply immediate payment collection: link with collections.
Minimum order
Block or alert below a threshold to preserve logistics profitability.
E-procurement
Carts guided by an approved catalogue on the buyer side: the OMS must respect the authorized lists and block off-contract references.
Integrations: ERP, 3PL, carriers and marketplaces
The OMS interfaces with the ERP (invoices, accounting inventory), the WMS or 3PL (shipping statuses), and the carriers (labels, tracking). APIs must handle retry, errors and daily reconciliation.
Status mapping
“Shipped” on the carrier side does not mean “delivered”: do not confuse this in the customer interface.
Tracking numbers
Surface them early in the store and support tools to reduce tickets.
Accounting entries
Sales date vs shipping date: rules to validate with Finance.
Project load
Each new connector is a mini-project: documentation, load tests, rollback plan.
Customs and documents
For international shipments, the order must include the correct HS codes and amounts: errors = blocked parcels.
Integration tests
Anonymized data sets to replay a typical day before going live.
Asynchronous queues
When a partner is slow, do not block the whole order: retry strategies and dead-letter queue for manual intervention.
Observability
Structured logs by order ID to investigate quickly during multi-system incidents.
Exceptions: fraud, addresses, outages and edge cases
Incomplete address, lost parcel, broken item, picking error: the « happy path » is not enough. Exception queues and roles (level 1 / level 2) speed up handling.
Fraud queue
False positives: protocol to unblock a legitimate customer without excessive delay.
Out of stock during order preparation
Offer substitution, delay, or partial cancellation with explicit consent.
Customer data
Same names, 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 manually expediting without breaking fairness with other customers.
Weather and force majeure
Storms, strikes: communicate realistic timelines and record decisions to respond to claims with verifiable facts.
Service continuity
Recovery plan if the main OMS is unavailable: buffer queue, read-only failover, or controlled manual entry so as not to lose critical orders during peak periods or a supplier incident. 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 coordinated in the admin. Specific features evolve: check the official documentation for your plan and your apps. For an assistant aligned with the statuses shown to customers: Qstomy integration on Shopify.
Fulfillment
Assign fulfillment to the right location or logistics partner: consistency with e-commerce fulfillment services.
Tags and workflows
Tag orders (VIP, supplier delay) for automations and reports.
Draft orders
Orders created by the merchant: useful for B2B and phone orders; process to avoid duplicates.
Documentation
Shopify: orders (documentation) as a starting 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 a custom solution.
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 so you can close the months without re-entering data.
Indicators, data quality and governance
Measure preparation time, picking error rate, canceled orders, exception resolution time. Cross-reference with your analytics reports to link product issues and customer support.
Address quality
Input-time validation reduces carrier returns: direct impact on cost.
Reconciliation
Compare paid, shipped, and collected orders: detect discrepancies early.
Roles and traceability
Know who changed a status or granted a discount: internal compliance.
Qstomy and support
Automated replies do not replace up-to-date statuses: synchronize chatbot content and OMS.
Weekly dashboards
Short ops / support / marketing meeting on the top reasons for cancellations and delays for corrective actions.
Living documentation
Update procedures when a new marketplace or a new carrier joins the scope.
Relationship with sales
Sales targets (volume, basket size) must remain compatible with fulfillment capacity: regular trade-offs between departments.
FAQ, summary and sources
Do you need an OMS from day one? Not necessarily; however, as soon as multiple inventories or channels intersect, a clear model becomes essential.
Who is responsible for the “official” order? Designate one system and export rules for the other tools.
How can WISMO be reduced? 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 short, e-commerce order management is the operational thread between customer promise and physical fulfillment: investing in clear statuses, robust integrations, and honest communication pays off more than simply stacking apps.
Further reading
The product catalog (already linked in the introduction) upstream determines the quality of order lines: consistent SKU, barcodes, and attributes prevent downstream errors.
In the short term, a procedures manual shared among support, warehouse, and finance is often better than a new tool that is poorly adopted.
Enzo
April 8, 2026
