A Sourcemap mock detention needs a reproducible evidence packet

Freeze the case before starting the clock

A mock detention should begin with a case manifest, not a broad supplier search. Freeze the importer, legal entity, product identifier, purchase order, shipment, entry or declaration reference, supplier facility, production lot, covered material, and the rule or inquiry being tested. Then record the request time, the precise evidence requested, the response deadline, and the person authorized to release each record. Sourcemap's current page describes transaction-level traceability and mock detentions; it does not establish what evidence any authority would accept for a particular entry.

Keep the transaction chain separate from the supplier map. A map may show that two entities are connected, while a detention response must usually reconstruct the material or product that moved in the tested transaction. Link each tier with dated commercial and logistics records, declared quantities, transformation or processing steps, facility identity, and document provenance. Preserve contradictions and gaps instead of filling them with an inferred relationship. A platform match or watchlist result can open the investigation; it should not silently become chain-of-custody proof.

Build a packet another reviewer can reproduce

The packet should contain an index, source files, translated copies where used, hashes or stable file identifiers, receipt dates, issuing parties, relevant transaction fields, redactions, and the link from each document to the product and shipment. Record the retrieval query and platform filters so another reviewer can rebuild the result from the same cutoff. If a supplier replaces a document or a late record arrives, retain both versions and show why the disposition changed.

Test failure paths deliberately: a supplier that does not respond, a facility name that differs across documents, a quantity that exceeds the upstream input, a broker file without manufacturer identity, and a document whose date falls after shipment. The drill should assign every exception an owner, escalation time, decision, and unresolved state. A green dashboard at the end is not enough; the retained evidence must show which questions were answered, which were not, and who accepted the remaining risk.

Separate readiness from authority acceptance

Measure the drill with operational facts: time to locate the case, time to assemble the first packet, percentage of required links backed by source records, unresolved identity conflicts, aged supplier requests, and time to an accountable disposition. Do not label the exercise successful only because the team exported a bundle before the deadline. Review whether the bundle was complete for the stated test, whether it could be reproduced, and whether legal, compliance, procurement, and logistics owners agreed on the response boundary.

Supply Chain Signal reviewed Sourcemap's registered official page on September 16, 2026. The source supports attributed claims about platform positioning and mock-detention workflows, not a conclusion about a particular importer, supplier, product, shipment, regulation, customs authority, detention, admissibility decision, or customer outcome. No attributable post-cutoff material news change was verified, so the public change ledger remains unchanged.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Supply Chain Signal will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.