Fashion-Supply Streaming Decision Architect — Global Retail

The mandate

The group receives purchase-order, production, inspection, shipment, customs, allocation and fulfilment events through different platforms, but their state transitions do not agree. Merchandisers therefore react to a nominally late collection that may be awaiting inspection, missing a partner update or genuinely delayed. Current streaming architecture moves messages quickly without establishing which decision each event authorises or reverses.

The deliverable is a Supply Decision Event Architecture for two seasonal collections, comprising canonical identities, state machines, contracts, ordering, correction, confidence, replay and consumer obligations. It must show how supplier and logistics evidence changes allocation, launch, markdown and customer-promise decisions. A reference stream and migration plan will preserve partner variation rather than mandate a single external system.

Milestone one in week four maps event journeys, decision points and contradictory states. Week nine closes milestone two with contracts, state models and replay design. At week sixteen, milestone three delivers shadow operation for both collections and tested disruption scenarios. Milestone four in week twenty-two provides the accepted architecture, partner scorecards, economics and internal migration governance.

Acceptance requires supply and merchandising teams to reconstruct twenty unseen item-location states, with every reversal and manual judgement visible; injected late or contradictory partner events must produce agreed decision warnings; and customer-promise teams must reproduce confidence. Architecture and Operations jointly sign after two external partners accept their contract obligations and an internal team replays a complete collection without consultant support.

The client will provide purchase orders, supplier milestones, inspections, logistics messages, allocation decisions, inventory, customer promises, interface agreements and incident histories. Merchandisers and regional supply teams will join journey observation; client engineers will implement the reference stream. The supply-chain chief will resolve disputed state meaning, while partner managers secure representative external testing.

Why this is external work

Messaging teams optimise transport, supply teams interpret physical events and merchandisers apply tacit commercial judgement; each sees a different failure. Existing integrators are attached to individual platforms and cannot neutrally define the cross-network decision model. External work supplies arbitration and contract evidence without assuming all suppliers can adopt one technology or cadence.

What you will own

• Trace collection, style, SKU, order, production lot, shipment, inventory and customer-promise states across every event-producing organisation.
• Define event contracts for identity, business meaning, occurrence time, publication time, correction, cancellation, confidence and source evidence.
• Build state machines that preserve partial, disputed and reversed progress instead of forcing every physical journey into nominal milestones.
• Link each state transition to allocation, launch, markdown, replenishment and customer-promise decisions with explicit consumer obligations.
• Test delayed inspection, split production, transshipment, customs hold, partial receipt and supplier correction through controlled replay.
• Price streaming choices across partner onboarding, exception handling, replay, support and avoided manual interpretation during seasonal peaks.
• Transfer contract governance, replay exercises and partner performance review to permanent supply-network and platform owners.

Candidate qualifications

• Designed event-driven supply platforms for fashion, retail, manufacturing or consumer goods spanning independent suppliers and logistics partners.
• Modelled physical item and order state where late, partial, contradictory and corrective events were normal rather than exceptional.
• Connected streaming semantics to commercial allocation or customer decisions instead of treating broker delivery as the business outcome.
• Negotiated practical contracts with partners having different systems, digital maturity, time zones and incentives to report progress.
• Built replay and shadow methods that exposed unsafe automated reaction before production adoption during a seasonal cycle.
• Delivered a vendor-neutral architecture that internal product and supply teams could govern after external engagement closure.

Non-negotiables

• The named architect must work with Milan merchandising teams and travel to representative supplier or logistics operations during the pilot.
• No reseller, implementation or referral economics may exist with brokers, integration platforms, control towers or supply-software vendors.
• Commercial state meaning remains accountable to client supply and merchandising executives, not inferred solely from technical event order.
• Supplier data must stay within approved regional and contractual boundaries throughout replay and shadow operation.

1. 49 words maximum. Describe a supply event whose technically correct delivery produced the wrong commercial state or action.
2. 49 words maximum. How would you model a collection item that is partially produced, re-inspected and split across shipments?
3. 49 words maximum. Which client inputs are essential to test whether an event should alter customer promise?