COMPLETED FIRST-RELEASE BRIEF — FICTIONAL DISTRIBUTOR
Horizon Dynamics | 5 October 2026 | Planning example, not an agreed specification

OUTCOME / OWNER
One operations team can follow accepted orders and resolve stock exceptions.
The client operations owner approves scope and workflow rules. A technical
contact provides API documentation and test access separately from this brief.

SYSTEMS / ONE INTEGRATION
Keep CRM and ERP. Send accepted CRM orders to ERP and return fulfilment status.
CRM owns customer assignments; ERP owns stock and reservations.
API support for the complete amendment flow is not yet confirmed.

FIRST WORKFLOW
Coordinator accepts order -> operations confirms stock -> ERP reserves ->
sales sees status under the same order reference. One team and warehouse.

TWO EXCEPTIONS
1. Insufficient stock: a named operations approver chooses split or delay.
2. ERP saves but acknowledgement is lost: retry without a second order.
Both exceptions have a visible status and responsible person.

THREE ACCEPTANCE CHECKS (PROPOSED, NOT EXECUTED)
1. Ten available, reserve four -> six available; request seven while the
   reservation remains -> agreed shortage route.
2. Deliver accepted order twice, including a lost-response retry -> one ERP
   order, with inspectable exchange status.
3. Restricted role cannot open/export a protected team's order. Authorised
   reviewer reconciles open-order report with the agreed source snapshot.

DATA / REPORTING
Transfer open orders and required customer/product references.
Historical attachments deferred. Report open-order exceptions with an owner,
UTC cutoff and visible source delay. Refresh requirement still to be agreed.

OUTSIDE THIS RELEASE
Ledger replacement, manufacturing, extra warehouses, customer portal and AI
actions. Included workflows still require testing, permissions and recovery.

COMMERCIAL / OPERATION
Budget and target date not approved. Estimate after API and source-sample review.
Agree hosting ownership, paid support coverage and transition window before launch.
No implied delivery date or savings.

NEXT DECISION
Bounded assessment: verify connector and mappings, confirm release boundary,
identify unresolved dependencies and estimate the agreed work.
Unknowns remain unknown until reviewed; this brief is not launch approval.

Adapt locally. Do not add credentials or real personal data to a public copy.
https://www.horizon-dynamics.tech/blog/prepare-custom-software-project