The paperwork is part of the product
A child-resistance certificate you cannot find on the day it is asked for might as well not exist. Compliance is not a drawer of PDFs: it is documents that live on the products they cover and travel with the order, and rules that announce their dates instead of arriving as surprises.
Nobody fails an inspection over a certificate they have. They fail over the one that exists in a folder on a laptop that belongs to somebody who left last spring. In this category the paperwork is not an accessory to the product - it is part of it, and it should behave like part of it.
Documents that live on the product
A certificate has a natural home: the product it certifies. Filed there once, it is findable by anybody, forever, from the thing itself - not from a memory of who downloaded it. The child-resistance certificate for a closure, the test report for a cartridge: they belong on the closure and the cartridge.
The same logic follows the goods out the door. When an order needs its papers - a buyer's compliance officer, a state inspector, an auditor - what they want is not a link and a promise. It is one packet: everything that covers this order, assembled together, with a record of what was in it and when it went out.
Rules have dates, not moods
State packaging rules are the other half, and the thing to hold onto is that a rule change is not weather. It is written down, it has an effective date, and the only question is whether you hear about it before that date or after.
- Before: it is a to-do. You run down the affected SKUs and adjust the next order.
- After: it is a rejected shipment, a relabelling bill, or stock you cannot sell in that state.
The rule did not change differently in those two stories. You just heard about it at different times.
What this looks like here
Certificates and test reports here attach to the catalog products they cover, and a buyer can see where each one stands from the product page - published, restricted, or requested and still waiting. When an order needs its compliance packet, the packet is a single download: the documents grouped by what they cover, catalog to item to lot to the order itself, and a snapshot records what went into it - so "what did we send them in March" has an answer months later.
State rules are versioned with their effective dates: a rule that has not bitten yet shows as upcoming rather than hiding until it does, and when one changes for a state you operate in, it reaches you as an alert. The week you find out is the week it was published - which is the cheap week to find out.