Applications · Order management
Take the order once. Promise a date you can keep.
Orders arrive from field sellers, distributor portals, marketplaces, email and the call centre, and are validated once, against credit, price and live stock. Allocation, fulfilment and the invoice trigger run on the same record, so nobody re-keys and nobody guesses a date.
multi-channel captureCredit & stock before the promiseAllocation & backorder rulesReturns on the same record
Operations & Finance · promise → recoveryCredit, stock, warehouse readiness and customer consequence meet before the date changes.SO-48211 · Held before release
13orders at risk₹8.4 Lblocked value94%fill rate
Line L20 · CT-902 / 6 ATP4 units unresolved · Bengaluru stock found
Promise12–13 Aug Freight₹19.8 K Margin14.8%
Customer consequenceFull launch set by 13 AugCredit release + Farah confirms transfer
Named authorityAnanya → Farah → Ritesh
9:41•••
Cutoff runway15:00→15:30→17:00transfer · pick wave · carrier
The order is not complete when it is captured. It is complete when the promise can be kept.
SO-48211 looks like one customer order. Operationally, it is a credit decision, four lines, two warehouses, a carrier hold, a store-opening date and three people who own different facts. Order Management keeps those facts on one record.
One order record
Dealer portal, marketplace, field and call-centre inputs resolve into the same order and line model.
SO-48211 · Dealer portalEvery constraint attached
Credit exposure, line ATP, warehouse readiness and carrier capacity stay visible before the date is confirmed.
₹2.90 L excess · 2 / 6 ATPThree viable paths compared
Delivery, freight, margin and customer effect change together when the recovery option changes.
3 paths · option B preparedThree owners keep the gate
Commercial, warehouse and order owners record different facts before allocation or customer notice can move.
Ananya → Farah → RiteshWhat changes
Keep the ledger. Move the promise into a living operating record.
These rows are the ones that decide whether a customer gets what was committed. Your ledger stays where it is: the process around it moves here.
Capture the commitment
Every channel writes one governed order.
Channel variety does not become record fragmentation. Validation, price, tax and duplicate checks converge before the order enters the promise.
Order capture
The SaaS playbook
→ A screen per channel, and re-keying between them.
Rebuilt agentic
Field app, partner portal, marketplace feed, email and call centre all write one order object with one validation path and one duplicate check.
Pricing & credit
The SaaS playbook
→ A price list, and a credit check somebody remembers.
Rebuilt agentic
Price, scheme and tax resolve on entry; credit limit, overdue exposure and blocked-party checks run before acceptance: a blocked customer cannot be promised stock.
Protect the promise
Availability becomes a dated operational fact.
ATP, allocation, warehouse and carrier constraints stay attached to the line that created the customer consequence.
Availability & promising
The SaaS playbook
→ Stock as of last night, and an optimistic date.
Rebuilt agentic
Allocation against live inventory and inbound supply, with backorder and substitution rules, so the committed date is derived rather than declared.
Fulfilment
The SaaS playbook
→ A pick list, a courier, and a phone call for status.
Rebuilt agentic
Pick, pack, dispatch and delivery states tracked to the invoice trigger, with the customer notified on their own channel, from the same record.
Recover with authority
An exception becomes a choice, not a hidden delay.
The recovery path names cost, customer effect and ownership before any release, communication or ledger trigger.
Exceptions
The SaaS playbook
→ A stuck order somebody notices on Thursday.
Rebuilt agentic
Short supply, credit block, price mismatch and address failure surface as owned exceptions with an SLA: each one routed, none parked.
Returns & claims
The SaaS playbook
→ A separate process, reconciled at month end.
Rebuilt agentic
Returns, shortages and damage claims raise against the original order line, so credit notes reconcile to the shipment that caused them.
The financial posting stays in your ERP or accounting system. Amoga owns the capture, the promise, the exceptions and the engagement around the order: the parts that are process, not ledger.
Change the path. See every consequence before the promise changes.
Compare recovery choices against ATP, freight, margin, customer effect and the authority still required. The selected path stays a proposal until all three owners record their decision.
Select a recovery path, inspect its evidence, then record (not execute) the owner review.Held before releaseReview recorded · still heldDecision trail active
₹21.80 L current; ₹24.90 L projected
2 Pune + 4 Bengaluru CT-90 available
Pick cutoff 15:30; order remains held
PNQ → JAI booking expires 17:00
All six CT-90 required before 14 Aug
Line L20CT-90 · 6
4 unallocated · Launch blocked without all 6
Ananya may release or return the credit hold; Farah confirms physical stock and transfer readiness; Ritesh selects the customer promise and communication. No credit release, allocation, shipment, promise change, or customer communication happens automatically.
CT-90 · 4 units needed
Bengaluru WH-02 · bin B-17
Scan four serials, isolate the tote, then return the readiness result to the order owner.
Option B prepared · split delivery 12–13 Aug · ₹19.8 K freight
Constraint evidence · one order thread
The promise is only as reliable as the evidence beneath it.
Credit exposure, location stock, the pick cutoff, carrier capacity and the customer launch note do not sit in separate inboxes. They remain cited on SO-48211, with a source and time.
Filter the evidence board. The order consequence remains visible while the source view changes.₹21.80 L current; ₹24.90 L projected
2 Pune + 4 Bengaluru CT-90 available
Pick cutoff 15:30; order remains held
PNQ → JAI booking expires 17:00
All six CT-90 required before 14 Aug
Credit release or return reason
Ananya records the credit release or return reason
Evidence carried into the decisionDeposit advice DA-884 · ₹3.50 L · bank confirmation still pending
Four serials scanned and tote isolated
Farah scans and isolates 4 × CT-90 at bin B-17
Evidence carried into the decision4 · Bengaluru WH-02 · Bengaluru WH-02 · bin B-17
Recovery path and communication accepted
Ritesh accepts a recovery path and releases the customer notice
Evidence carried into the decisionNorthstar needs all six kits before its 14 Aug store launch.
Prepared work · bounded authority
One recovery does not mean one approval.
Ananya owns commercial exposure. Farah owns the physical-stock fact. Ritesh owns the customer commitment. Their decisions meet on the order without being collapsed into an opaque “approved” state.
Move across the authority rail to inspect what each owner sees and what remains outside the agent’s authority. Warehouse companion · the physical fact
The critical evidence arrives where the stock actually sits.
Farah does not approve a diagram from a desk. She scans four CT-90 serials at bin B-17, isolates the tote and returns a readiness result to the order owner. The proposed path remains held.
Web context and mobile intervention remain two views of SO-48211, not two disconnected workflows.9:41•••
Bengaluru WH-02 · bin B-17
Scan four serials, isolate the tote, then return the readiness result to the order owner.
Serial 01Serial 02Serial 03Serial 04
Farah Khan→Ritesh Soni
The order desk, generated.
Your order types, tax treatment, credit policy and fulfilment models are configured in the session. The customer, order, line, stock source, promise and decision trail remain connected because they are not reconciled after the event.
Order types & templates
Standard, rush, sample, replacement, consignment and subscription orders, each with its own validation and approval path.
type · validate · approvePricing & schemes
Price lists by segment, currency and period, with slab discounts, scheme entitlement and margin floors enforced at entry.
list · slab · floorCredit control
Limits, ageing exposure, security deposits and hold rules, with a release path that follows the authority matrix.
limit · exposure · releaseAllocation & ATP
Availability across locations and inbound supply, allocation priority by customer class, and substitution and backorder rules.
atp · priority · backorderFulfilment tracking
Pick, pack, dispatch, in-transit and delivered states with proof of delivery, partial shipments and split consignments.
states · pod · partialCustomer engagement
Order confirmations, dispatch alerts and delay notices on the customer's own channel, plus a self-serve order status portal.
notify · portal · statusReturns & credit notes
Return authorisation with a reason code, inspection outcome, and a credit note referencing the original order line.
rma · inspect · creditOrder control tower
Live view of orders at risk by value, ageing exception queues, and fill-rate and on-time-in-full reporting by customer.
at risk · fill rate · otifPromise capture → controlled release
An order that hits a credit block and still moves.
Execution remains visible rather than collapsing into an automatic status change. Each constraint, prepared recovery and owner decision stays attached to SO-48211.
“which orders will miss their promised date this week, and what is blocking each”Prepared by the system · released only through the named human gate
Order inFIELD · PORTAL · MARKETPLACE
↓Intake agentPRICE · TAX · DUPLICATE
↓Credit & stock ok?EXPOSURE · ATP
↓Commercial headRELEASES THE HOLD
↓Allocate & dispatchPROMISE DATE · POD
↓Invoice triggeredTO THE LEDGER · TRAIL PINNED
Three agents on the order. Commercial keeps the release.
Agents prepare evidence and recovery work inside the order record. The authority that changes commercial exposure, stock, shipment or customer commitment remains human.
Normalises orders from every channel, resolves price, tax and scheme, and catches duplicates before they ship twice.
mismatches shown, not guessedWorks the exception queue: short supply, address failure, price mismatch, and proposes the resolution with its cost.
each exception has an ownerWatches every committed date against fulfilment reality and warns the customer before they have to ask.
notice goes out on approvalClassifies return reasons, checks entitlement, and links the credit note back to the shipment that caused it.
credit release follows the matrix
Bring one order type. Watch it promise a real date.
A 90-minute working session: your order types, credit policy and allocation rules drafted as an FRS, approved, and generated to a staging tenant with the exception queue running.
For your technical team
Order management is meta on the platform: the same customer record as the CRM, the same inventory model as the warehouse, and durable execution behind every promise, with the financial posting left to your ledger.