OpsGrid · Logistics & 3PL · Dynamics 365 Business Central required · Active Beta

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.

Signal Route Approve Execute Audit
Book a live OpsGrid demo with logistics data →
What OpsGrid surfaces from BC

Three logistics signals in Business Central right now — none with an owner

OpsGrid monitors BC continuously. When a threshold is crossed, it ranks the signal by cost impact and sends it as an actionable card to the named owner in Teams.

Delivery exception
SH-2026-0441 — Customer commitment needed
  • Carrier reported delay — new ETA 4 days out
  • Customer SLA: 2-day delivery committed
  • Exposure: $18,600 order + SLA penalty clause active
Critical · Unrouted
Invoice mismatch
INV-8842 — $2,800 variance unresolved
  • Carrier invoice $2,800 above agreed rate
  • In Finance queue for 9 days — no action taken
  • Carrier threatening to hold next shipment
Warning · No decision
Overdue purchase order
PO-2026-0091 — 6 days past expected receipt
  • Carrier hasn't responded to 2 follow-up emails
  • Downstream production run dependent on receipt
  • No escalation owner assigned in BC
Warning · No decision
How OpsGrid closes the gap

Exception to decision in Teams — not in a shared inbox

Signal

BC flags a delivery exception, invoice mismatch, or overdue PO. OpsGrid ranks by cost impact and picks up the signal within minutes.

Route

Logistics Coordinator gets delivery exceptions. Finance Lead gets invoice mismatches. Warehouse Manager gets overdue receipts. One person per signal. SLA clock starts immediately.

Approve in Teams

Owner reviews the recommended action in Teams — issue credit note, approve mismatch payment, escalate carrier. No BC login. One tap to approve, reject, or escalate.

Execute

Approved action writes to BC — credit note created, invoice approved, PO escalation logged. Nothing posts without explicit approval.

Audit

Every exception decision logged — who acted, when, what data they saw, what the outcome was. Customer disputes have a documented trail.

OpsGrid doesn't replace your TMS or WMS. It governs the BC-facing decisions that cross from those systems — the order updates, invoice approvals, and PO escalations that require a named human with authority to act.
Decision owners by signal type
Logistics Coordinator Warehouse Manager Finance Lead COO (escalation)

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. It doesn't set an SLA. It doesn't escalate when nobody responds. 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 OpsGrid governs in logistics
Delivery exception routing to Logistics Coordinator
Invoice mismatch to Finance Lead with approval path
Overdue PO escalation with carrier context
COO escalation if SLA missed
Full audit trail — every exception, decision, outcome
Common questions

What logistics operators and 3PLs ask before deployment

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 governs the decisions that cross from those systems into BC and require a named human to act.
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, escalate to finance) to the named owner. The exception still gets resolved faster because the BC action has an owner with an SLA.
Yes. Decision routing in OpsGrid is configurable by customer, shipment type, value threshold, or any combination. A 3PL with 8 clients can route each client's exceptions to the right account manager, with client-specific SLAs and escalation chains. The audit trail is separated by client. Configuration happens in Week 1.
Three weeks. Week 1: BC APIs enabled, service account provisioned, decision types configured — delivery exception thresholds, invoice mismatch limits, overdue PO escalation rules, 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 60 days or we refund 50% of implementation cost.
OpsGrid for other verticals
Manufacturing
Production delays and cost variances that surface in BC Tuesday and land with the plant head Friday.
View manufacturing →
Distribution
Credit holds, backorder SLAs, and pricing decisions that stall in BC for days.
View distribution →
Security & Architecture
How OpsGrid connects to BC, what it reads, and what it never writes without approval.
View architecture →
OpsGrid Overview
Decision infrastructure for all BC operators. Signal, route, approve, execute, audit.
Back to OpsGrid →
Active Beta · Logistics & 3PL

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 in 60 days or 50% refund.

Book a live demo with logistics data →