160 units
Country placeholder: FR
Needs verification
Fictional/composite workflow sample • published 19 July 2026 AEST
A route type is not a recipient. Make every evidence gap visible.
A founder-readable LaunchReady sample for teams building public-source deadstock routing briefs: five fictional paths, zero claimed recipients, explicit missing fields, and a deterministic verification gate.
One fictional 500-unit request, five research lanes
This fixture illustrates a delivery schema only. It does not identify an actual retailer, inventory lot, recipient, or available route.
120 units
Country placeholder: DE
Needs verification
80 units
Country placeholder: NL
Needs verification
90 units
Country placeholder: ES
Needs verification
50 units
Country placeholder: FR
Needs verification
Blank fields are a product feature
Scenario fields
route_type, country placeholder, product category, and allocated quantity.
Recipient evidence
Recipient name, public evidence URL, observed acceptance criteria, and verification date.
Operational conditions
Minimum batch, logistics scope, timing, custody, cost, and proof document.
Legal and exception questions
Eligibility, cross-border, tax, liability, brand protection, and any exception interpretation.
The validator requires every fictional row to remain needs_verification. It counts missing evidence instead of estimating it.
The founder-readable five-bullet review
1
Start with a route request, not a directory row
Capture category, quantity, condition, restrictions, location, timing, and desired evidence before presenting candidate paths.
2
Separate route class from recipient eligibility
“Donation” or “remanufacture” is an option class. It is not evidence that a specific organisation accepts this category, batch, geography, or condition.
3
Version evidence and freshness
Store source URL, observed conditions, geography, minimum batch, verification date, and human re-check status. Leave unknowns missing.
4
Keep legal judgment outside automation
The ledger can prepare evidence and provider questions. It must not decide compliance, tax, shipment, liability, brand protection, or exception eligibility.
5
Sell a bounded brief before a marketplace
The paid wedge is a country/category source map, verified-candidate shortlist, missing-field report, change log, and provider-ready questions—not custody or guaranteed placement.
Why this signal matters—without overclaiming
The source context is the European Commission notice on the rule entering application, its background notice, and France's AGEC policy context. These sources motivate research; they do not verify any route in this fixture.
A$149–299 Routing Data Product Readiness Review
One public or redacted workflow plus one sample ledger, returned in 48–72 hours with a request schema, evidence and missing-field policy, verification statuses, claims edits, paid-brief packaging, and a next-distribution queue.
One public or redacted workflow plus one sample ledger, returned in 48–72 hours with a request schema, evidence and missing-field policy, verification statuses, claims edits, paid-brief packaging, and a next-distribution queue.
Boundary: public or explicitly supplied redacted evidence only. No legal, tax, customs, environmental, logistics, brokerage, certification, disposal, or compliance advice; no recipient contact or inventory movement; no guarantee of acceptance, route availability, outcome, cost, coverage, or buyer response.