Integration guide
Inventory reorder
Review a replenishment proposal before approval.
Calculation and alert helpers exist; real source data, delivery and purchase-order execution are not qualified here. Confirm the owner, permissions and a real acceptance test before relying on a connection.
Start with a retail decision
Choose the review
Review a SKU threshold breach with the forecast, current stock and a named approver.
Make the evidence comparable
Validate units and input dates, alert throttling and the purchase-order approval boundary.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
Output scope to review: Reorder-point calculation and alert candidate for human approval
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Tenant · SKU · lead time · forecast · stock level · threshold · approval owner | Read an agreed sample | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
Calculation and alert helpers exist; real source data, delivery and purchase-order execution are not qualified here.
Do not send passwords, API keys or customer records through the contact form.