The exception inbox: what needs a decision, with the fix attached

Why exceptions instead of dashboards?

A dashboard answers "how are we doing?" It does not answer "what is broken, and what do I do about it?" Operations teams at growing brands already have plenty of charts. What they lack is time to read them closely enough to notice the one SKU whose 3PL count stopped matching, or the purchase order that slipped two weeks.

SuppliFlex starts from the other end. When something in the system of record stops adding up, it becomes an item in the exception inbox. The inbox is the to-do list; the dashboard is context. If the inbox is empty, nothing needs you.

What lands in the exception inbox?

Three kinds of problem, all in one list:

• Discrepancies: two numbers that should agree and do not, such as a stock count against the ledger.
• Conflicts: two sources reporting different values for the same record.
• Failed syncs: an update a channel, carrier, 3PL or accounting connector did not accept.

Every item carries the cause in plain terms and a one-click fix. You do not need to open three systems to work out what happened before you can act on it.

What do the alerts look like?

Two examples show the range.

Oversell risk when channel demand spikes. A product starts selling much faster than usual on one marketplace. Available stock is shared with your other channels, and at the new pace it will run out before the next receipt. Seeing the risk before stock runs out is what makes the decision cheap: hold back a channel, move stock or expedite a purchase order. Which of those makes sense is a business call, and the inbox puts it in front of the person who makes it.

A supplier missing delivery windows, with a projected stockout date. A supplier's recent deliveries have arrived later than agreed. SuppliFlex tracks that lead-time drift automatically, and the alert carries a projected stockout date. Instead of finding out from an empty shelf, you see the date weeks ahead and can chase the supplier or place a bridge order. The tracking itself is part of purchasing.

What does "always ask" mean during the beta?

When two sources disagree, there are two ways to settle it: a rule picks the winner, or a person does. During the production beta, which starts on 13 November 2026, SuppliFlex uses one policy for conflicts: always ask. The conflict appears in the inbox with its cause, and nothing is overwritten until someone chooses.

That is slower than an automatic rule on paper. In practice it stops a single bad value, such as a mistyped count or a stale marketplace figure, from spreading to every channel through real-time sync. Design partners running SuppliFlex as their system of record will see every conflict rather than finding out later that one was resolved the wrong way.

How are recurring exceptions handled?

Some exceptions come back. The same SKU drifts at the same 3PL, or the same marketplace rejects the same field. SuppliFlex adds task queues and a knowledge base for recurring exceptions, so the team does not work out the cause from scratch each time and the person who fixed it last month is not the only one who knows how.

Who sees the inbox?

The dashboard adapts by role, with views for ops, founders, finance and warehouse staff, and it leads with what needs a decision today. A warehouse lead and a finance lead look at the same system of record but are not shown the same list of priorities.

Where can I try it?

The sandbox opens on 30 October 2026. It runs the real product on seeded data, and a SuppliFlex-hosted simulator sends Shopify, Amazon, QuickBooks and carrier events every few minutes. The food and beverage seed pack includes supplier lead-time drift and the electronics pack includes marketplace spikes, the same situations behind the two example alerts.