OpsGrid · Distribution · Dynamics 365 Business Central required · Active Beta

PARIS-CHAIR runs out in 3 days. Business Central knows. Nobody owns the reorder.

6 units on hand, 14 on open orders, 11 days to replenish. Business Central warns whoever enters the sales order that stock will run short. The buyer still finds out when the order can't ship. OpsGrid names who reorders: one Purchasing Lead gets the approval in Teams, and Approve creates the Draft PO in BC. Credit-hold routing is on the roadmap.

Signal Route Approve Execute Audit
Book a live OpsGrid demo with distribution data →

Illustrative panels on sample data. Some show planned features, such as credit-hold and backorder routing, that are on the roadmap and not live in the beta today.

What OpsGrid surfaces from BC

Three distribution 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.

Credit hold
NORTHWIND TRADING: $47,200 blocked
  • 3 orders on hold, 72 hours unresolved
  • Customer paid last invoice 8 days ago
  • Credit Controller reviewed, Finance approval pending
Critical · Unrouted
Inventory risk
PARIS-CHAIR: Stockout in 3 days
  • Current stock: 6 units. Open orders: 14 units
  • Replenishment lead time: 11 days
  • Exposure: $18,600 in unfulfillable orders
Critical · Unrouted
SLA breach
14 backorders: past promised date
  • Average delay: 4.2 days past commit
  • 3 customers have escalated to account manager
  • Exposure: $31,000 in delayed revenue
Warning · No decision

Illustrative panels on sample data. Some show planned features, such as credit-hold and backorder routing, that are on the roadmap and not live in the beta today.

How OpsGrid closes the gap

Signal to decision in Teams, not in an email chain

Signal

BC crosses a stockout or reorder threshold. OpsGrid picks it up at its next scheduled check and ranks it by revenue impact.

Route

Inventory Manager gets stockout risk. Purchasing Lead gets replenishment signals. Credit Controller will get credit holds once that signal ships. One person per signal.

Approve in Teams

Owner reviews the recommended action in Teams: approve a transfer or a reorder. One tap to approve or reject. Approved items land in BC as drafts for confirmation.

Execute

Approved action goes to BC as a draft: a purchase order or transfer order with its lines filled in. A person confirms and submits it in BC.

Audit

Every decision logged: who released the hold, when, what BC data they saw, what orders shipped next.

No rip-and-replace: OpsGrid works alongside your existing BC setup. Pricing tables, margin rules, credit limits: none of it changes. OpsGrid governance sits on top, not inside the configuration.
Decision owners by signal type
Credit Controller (on the roadmap) Inventory Manager Purchasing Lead CFO escalation (on the roadmap)
Roadmap

Credit holds: on the roadmap

OpsGrid will route each credit hold to one named Credit Controller in Teams; that signal is not live in the beta today. Join the waitlist and name credit holds as the signal you need.

We already have BC reports. Why do we need a governance layer?

BC reports show what happened. They don't assign a decision owner, and they don't execute the approved action. A stock report tells you an item is running low. It doesn't tell the Purchasing Lead to act, give them a one-click approval path, or draft the PO in BC when they do.

The gap isn't data: it's accountability. Which person owns this signal? Who approved what, and when? The report can't answer either question.

OpsGrid turns BC data into decisions with named owners and an audit trail. The report stays. The decision gets governed.

What OpsGrid governs in distribution
Credit hold routing to Credit Controller (on the roadmap)
Stockout signal to Purchasing Lead with draft PO
Backorder SLA breach to Account Manager (on the roadmap)
CFO escalation past a response window (on the roadmap)
Full audit trail: every decision, release, rejection
Common questions

What mid-market distributors ask before deployment

Does OpsGrid touch our pricing or margin configuration in Business Central?

No. OpsGrid reads BC data: credit balances, order status, stock levels, backorder age. It surfaces decisions and routes them to named owners. Pricing tables, margin rules, and credit limits stay exactly where you set them in BC. OpsGrid has no write access to configuration. The only writes it makes are operational, such as draft transfer orders and purchase orders, and only after explicit human approval.

We have 40 active customers. Will OpsGrid create noise?

Signal thresholds are configurable per decision type. You set the stockout warning level for each item group. Credit-hold and backorder thresholds will be set the same way once those signals ship; both are on the roadmap. You don't get a card for every minor event: you get a ranked list of the highest-cost unresolved decisions, routed to the right person. As an indicative range for a mid-market distribution deployment: 3 to 8 actionable signals per day.

Our purchasing lead is part-time. How does routing handle that?

Today each decision type routes to one named owner, set during Week 1. If your purchasing lead is part-time, name the person who covers on their off days as the owner for that decision type. Backup owners, automatic escalation and credit-hold routing are on the roadmap.

How long does deployment take for a mid-market distributor?

Three weeks. Week 1: BC APIs enabled, service account provisioned, decision types configured: stockout warning levels and one named owner per decision type. Week 2: Teams webhook live, approval routing confirmed. Week 3: Go-live walkthrough with your team, first live signals reviewed, routing adjustments complete. Measurable ROI within 90 days of moving to production, or we refund 50% of implementation cost.

Active Beta · Mid-market distribution

See your BC distribution 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.

Book a live demo with distribution data →