Channel-aware orders with duplicate protection, stock authority and payment reconciliation.
A seller operating across marketplaces needs to preserve each channel's order identity, deadlines and financial evidence. The E-commerce Order Management design brings those obligations into an order desk while keeping account-specific rules visible. Each marketplace connection requires its own supported API permissions, mappings and reconciliation tests. Choose the connections and account scopes needed for the marketplaces your business uses.
The same external order number may exist in different marketplace accounts. Channel plus external order identity identifies the purchase, while channel plus event identity handles repeated deliveries. A duplicate retry cannot create another order or another warehouse instruction.
Marketplace stock publication and order allocation need an agreed authority. If another channel can consume units outside that authority's reservation protocol, the system cannot guarantee exclusivity from a local snapshot. Stale stock and conflicting commitments require review before promising more inventory.
Dispatch cutoffs, accepted cancellation methods and customer communication rules are configuration inputs. The order desk preserves evidence of the current obligation and the source revision. A local cancellation stays pending while accepted warehouse work still needs an external outcome.
Split packages retain the original channel line identities and shipped quantities. Shipment updates return through the configured adapter with stable command identities. A failed acknowledgement remains recoverable without creating a second shipment or discarding the outstanding balance.
Payment state uses verified provider objects. Marketplace settlement fees, withheld balances and tax remittance remain the responsibility of the configured financial authority and accounting integration. A refund request has its own decision and external result; an accepted return does not prove the customer has received money.
Same records, same gates. The configuration changes how the process runs for this team.
Review refund request waits for the finance reviewer.
Illustrative preview · actions are unavailable here.
Owns customer requests, source corrections and evidence of customer agreement.
Allocates stock and manages uncovered demand.
Decides order risk, price exceptions and customer-facing amendments.
Maintains mappings and resolves transport and reconciliation failures.
Approves bounded refund instructions and reconciles financial outcomes.
Warehouse release, split shipments, tracking and cancellation acknowledgement.
Order, stock, delivery and refund reporting with explicit unresolved outcomes.
Order intake with channel identity, commercial checks, approvals and traceable amendments.
Price snapshots, customer agreements, discount exceptions and refund allocations.
Available-to-promise, reservations and backorder resolution grounded in stock authority.
Return authorisation, inspection, disposition and independently approved refunds.
Compare first accepted promise and latest agreed promise with evidenced delivery; retain revised commitments and exclude unconfirmed tracking outcomes from on-time claims.
Compare active reservations and pending dispatch debits to authority snapshots, highlighting stale stock and unacknowledged movements.
Show dispatch count and recorded carrier charges per order when a configured cost source supplies them; missing costs remain unknown.
Keep location-specific reservations and fulfilment instructions under the same customer order. Each shipment retains its original line identity and actual quantity. Remaining demand stays visible until it ships or is validly cancelled, and external warehouse acceptance is recorded separately from local release.
Related questionChannel plus external order identity identifies the canonical purchase. Channel plus event identity identifies each intake delivery. An unchanged repeated event returns its previous result; a changed payload under the same identity becomes a conflict. These requirements must be enforced atomically and tested against the actual channel adapter.
Related questionA stock observation alone cannot guarantee that another system will not sell the same units. Automatic available-to-promise requires current sellable stock and a reservation protocol shared by all competing writers. Otherwise the system must show unconfirmed availability and require review instead of making an unsupported promise.
Related questionA backorder records uncovered demand, an owner, supply evidence and a next review date. Its expected replenishment date can remain uncertain. A customer promise is a separately accepted commitment, with the original date and subsequent customer responses retained for follow-up and reporting.
Related questionProduct substitutions require explicit customer consent to the proposed SKU, quantity and price difference, plus independent commercial approval. A short pick cannot silently substitute another variant. The approved replacement remains traceable to the original line and must pass its own availability check.
Related questionThe order desk submits a revision-bound change. Once a warehouse has accepted the work, cancellation waits for its actual response and stock remains committed. A refusal or dispatch race leaves the affected quantity on the shipped or outstanding path; goods already dispatched may require a return.
Related questionNo. Return authorisation, inspection, stock disposition and refund approval are separate actions. Finance Reviewer approves another requester’s exact refund revision within verified captured value and refundable components. The external provider result establishes whether money was actually refunded.
Related questionThe refund remains Unknown while its capacity stays reserved. The original immutable command and provider key are retained. Reconcile the provider object before creating a different attempt or releasing the amount; a timeout alone is not evidence that the provider did nothing.
Related questionConfigure connections for the order channels, stock authorities, warehouses, carriers, payment providers and accounting systems your business uses. Agree each provider’s supported actions, account permissions and record mappings during setup.
Related questionProto can help propose and configure changes on a branch for review. Changes that affect quantity rules, approval scope or provider behavior must update the specification and acceptance cases together. Existing source identities and audit history remain intact, and machine work follows the applicable usage pricing.
Related questionOrder operations for product brands balancing promotions, promises and customer returns.
Channel-aware orders with duplicate protection, stock authority and payment reconciliation.
Stock allocation and partial fulfilment across owned and partner warehouses.
