Monday morning. Twelve exception threads. Five systems. Zero pallets moved.
SH-2026-0441 needs a customer decision. INV-8842 has a $2,800 mismatch Finance hasn't touched. PO-2026-0091 is 6 days overdue and the carrier hasn't responded. Three decisions. No named owner for any of them.
Book a live OpsGrid demo with logistics data →Three logistics signals in Business Central right now: none with an owner
OpsGrid checks BC on a schedule (every 6 hours planned). When a threshold has been crossed, it ranks the signal by cost impact and sends it as an actionable card to the named owner in Teams.
- Carrier reported delay, new ETA 4 days out
- Customer SLA: 2-day delivery committed
- Exposure: $18,600 order + SLA penalty clause active
- Carrier invoice $2,800 above agreed rate
- In Finance queue for 9 days, no action taken
- Carrier threatening to hold next shipment
- Carrier hasn't responded to 2 follow-up emails
- Downstream production run dependent on receipt
- No escalation owner assigned in BC
Exception to decision in Teams, not in a shared inbox
BC flags a delivery exception, invoice mismatch, or overdue PO. OpsGrid picks up the signal at its next scheduled check and ranks it by cost impact.
Logistics Coordinator gets delivery exceptions. Finance Lead gets invoice mismatches. Warehouse Manager gets overdue receipts. One person per signal. SLA clock starts immediately.
Owner reviews the recommended action in Teams: issue credit note, approve mismatch payment. One tap to approve or reject. Drafts land in BC for a final check.
Approved action writes to BC: credit note created, invoice approved, PO escalation logged. Nothing posts without explicit approval.
Every exception decision logged: who acted, when, what data they saw, what the outcome was. Customer disputes have a documented trail.
We already track exceptions in a shared inbox. What does OpsGrid add?
A shared inbox shows that the exception exists. It doesn't assign a decision owner, and it doesn't execute the BC action when someone finally decides.
The shared inbox is where exceptions go to age. OpsGrid is where they go to get resolved, with a named owner, a response window, a one-click action in Teams, and a write to BC when approved.
The difference isn't visibility. It's accountability. Shared inboxes distribute responsibility so broadly that nobody owns anything. OpsGrid assigns one person per signal. That person has a SLA. The audit trail shows whether they hit it.
What logistics operators and 3PLs ask before deployment
Does OpsGrid replace our TMS or WMS?
No. OpsGrid connects to Business Central: your system of record for orders, receipts, and financials. It surfaces BC-facing decisions: delivery exceptions that need a customer commitment, invoice mismatches that need finance approval, purchase orders that are overdue and need a carrier escalation. Your TMS handles dispatch routing. Your WMS handles warehouse operations. OpsGrid reads Business Central only, so it governs the decisions that land in BC and need a named human to act.
We use a third-party carrier portal alongside BC. How does OpsGrid handle data from outside BC?
OpsGrid reads from Business Central. If carrier status is imported into BC (via EDI, API, or manual update), OpsGrid can surface it. If the carrier portal is completely separate and never posts to BC, OpsGrid won't see it directly. In that case, the value is on the BC-facing side: when a delivery exception arrives, OpsGrid routes the BC-side decision (update order status, issue credit note) to the named owner. The exception still gets resolved faster because the BC action has a named owner.
We run multiple clients out of one BC environment. Does OpsGrid support that?
Today OpsGrid routes each decision type to one named owner. Routing by customer, shipment type or value, and client-specific escalation chains, are on the roadmap. The audit trail is separated by client. Configuration happens in Week 1.
How long does deployment take for a logistics operator or 3PL?
Three weeks. Week 1: BC APIs enabled, service account provisioned, decision types configured: delivery exception thresholds, invoice mismatch limits, routing chain per client or signal type. Week 2: Teams webhook live, approval routing confirmed. Week 3: Go-live walkthrough with operations team, first live signals reviewed, routing adjustments complete. Measurable ROI within 90 days of moving to production, or we refund 50% of implementation cost.
See your BC exception signals routed to the right person in one session
We start with a free Decision Latency Audit: map where your BC data is getting stuck and put a number on it. No commitment until you see the cost. Dynamics 365 Business Central required. 3-week deployment. ROI on one agreed use case within 90 days of production, or 50% refund.