Skip to content
Business problems / Retail, wholesale and distribution teams
Custom system design

Supplier changes keep breaking our promises

Keep open quotes, stock allocation and delivery promises aligned when a supplier changes stock, cost or campaign terms.

A situation to work through

A walk-in sale takes the last local unit. An online order is still open, and the supplier campaign ends tonight.

Illustrative workflow design

Supplier stock and pricing change control

  1. Detect change
  2. Find affected work
  3. Recheck rules
  4. Approve alternative
  5. Confirm fulfilment
Choose what happens next
What happened
A supplier sends a current stock and campaign file.
What the system checked
Match supplier items to sellable SKUs; check effective dates, stock source and open quotes.
Next action
Prepare eligible updates and flag quotes whose assumptions changed. Release only actions permitted by the agreed rules.
What is recorded
Input snapshot, affected records, rule version and each accepted update.
Controls and integration

Source timestamps, reservations, price validity, margin thresholds and authority to change an accepted promise. A supplier quantity is not a reservation.

Connect to existing systems where their APIs and permissions allow. Rules, approvals, reconciliation and recovery are agreed before any production write. AI may extract or classify; validated business rules control consequential actions.

Illustrative rules and records. This demonstration does not connect to your systems or claim a measured client result.

Evidence before promises

Agree what a better result means.

Track affected open orders, time to resolve and contribution margin after freight, discounts and credits. Model handling time here; measure margin separately.

  1. Active minutes per supplier update batch, including exceptions.
  2. Affected orders resolved before dispatch; overdue promises still open.
  3. Realised margin on comparable orders after delivery and credit costs.

Capture a representative baseline, including difficult cases. Compare the same work mix after release and count review, rework and upkeep. Agree a measurement period that fits your volume.

Before you build

Before applying this to your business

The decisions and evidence to settle before a production rollout.

Should supplier availability count as stock we can promise today?

Keep owned stock, reservations and supplier availability separate. A supplier feed needs a freshness check, fulfilment policy and any order confirmation required before a delivery promise. A stale or missing feed should make availability uncertain rather than quietly keeping the last positive quantity.

What happens to accepted orders when a supplier changes a price?

An agreed policy distinguishes new enquiries, unaccepted quotes and accepted orders. A new supplier price must not silently rewrite a customer’s accepted terms. Recalculate the affected margin, identify the owner and prepare an authorised alternative or customer discussion where the original promise can no longer be met.

How can we prove the stock process is improving?

Compare the same supplier batches and order mix before and after launch. Track source freshness, mismatches, orders held for investigation and human handling time, including exceptions. Fewer manual edits alone do not establish more accurate availability or improved fulfilment.

Make it specific to your business

Start with one bounded piece.

Start with one supplier and one order channel. Detect changes and prepare decisions in review mode before enabling stock or price updates.

How it connects · existing software, n8n and custom code

We first check what your current software already supports. Where it fits, n8n can coordinate steps alongside native integrations and custom code. You do not need to choose the technology before describing the problem.

The scope identifies data access, credentials, approvals, monitoring, failed-action recovery, hosting, licence costs and who maintains the system. Handover covers the agreed workflow definitions, code, operating notes and access. Customer-controlled infrastructure can be considered where appropriate.

n8n has cloud and self-hosted options; some team and governance features require a paid plan. The appropriate edition and responsibilities are confirmed during scoping. n8n deployment options.

Go deeper

The workflows behind this outcome.

Explore related systems →