DEV Community

life
life

Posted on

Model a trademark detention as two clocks and five disclosed fields

A customs detention looks like one event from the outside. A shipment stops, somebody sends a letter, the goods either move or they do not. Once you read 19 CFR part 133 as a data model, that single event decomposes into two independent timers, a fixed set of fields that leave your control, and a status that can flip long after the goods were delivered. A boolean column called customs_hold collapses all four of those into something you cannot query when it matters.

Two timers with different start events

The first clock belongs to CBP. Under 19 CFR 133.21(b)(2)(i), the agency has five business days from the date of its own decision to detain in order to notify the importer in writing. The trigger is the internal decision, not the shipment date and not the postmark, so the start of that interval is not observable from your side of the fence.

The second clock belongs to you. The same paragraph gives the importer seven business days from notification to present information showing the detained goods do not bear a counterfeit mark. That is the only window in the section where additional evidence changes what the rights holder gets to see. Miss it and 19 CFR 133.21(b)(2)(ii) has CBP continue with disclosure to the owner of the recorded mark whenever the extra information would help and would not disturb an ongoing investigation.

Store both as separate timestamp pairs: detention_decision_date and notice_received_datetime. Deriving one from the other is exactly the modeling error that makes these deadlines unmanageable. A notification that arrives four business days after the decision leaves you the same seven business days, but a report that shows only "days on hold" cannot tell you that.

The 30 day detention ceiling in 19 CFR 133.21(b)(1) runs from a third event entirely, the date the merchandise is presented for examination. Three start events, three fields.

Five fields the rights holder may see before you do

19 CFR 133.25(b) enumerates what CBP may disclose to the owner of a recorded mark or trade name between presentation for examination and issuance of the detention notice. The list is short enough to treat as a schema: importation date, port of entry, merchandise description, quantity, and country of origin. Section 133.25(c) goes further and permits a sample of the suspect merchandise to be released to that owner before any seizure happens, and 133.21(b)(3) covers information visible on the goods or their retail packaging, including unredacted photographs.

For an engineering team the implication is concrete. Those five values are not read out of your warehouse system, they are read out of whatever you submitted: the entry paperwork, the manifest, the advance electronic data. When your internal record and the submitted record disagree, the rights holder sees the submitted version first and you get seven business days to explain the difference.

That makes the useful artifact a captured snapshot rather than a live join. At the moment a shipment is handed to a carrier, freeze the description, value, quantity, origin statement and packaging imagery you actually transmitted, keyed by shipment, and keep the frozen copy immutable. Twelve months later a live query against current product data answers a different question than the one CBP asked.

Release is not a terminal state

Two sections break the intuition that a released shipment is finished.

19 CFR 133.26 deals with merchandise that has already left CBP custody and is later found to fall under those three restriction sections. An authorized official makes a prompt demand for redelivery, and the demand reaches the bond. In state machine terms, released is not a final state. There is an edge from released back to action_required that can fire much later, and the event that triggers it comes from the agency, not from your system.

19 CFR 133.27 adds a second actor set. The civil fine authority under 19 U.S.C. 1526(f) reaches any person who directs, provides financial or other assistance to, or aids and abets the importation for sale or public distribution of merchandise bearing a counterfeit mark. Party roles in your schema therefore need to distinguish who is importer of record, who instructed the movement, and who paid for it, because the regulation does not limit consequences to the entity named on the entry.

What the relief paths actually require

Where a mark copies or simulates a recorded mark rather than being counterfeit, 19 CFR 133.22(c) offers a few exits: the offending mark removed or obliterated so it is illegible and cannot be reconstituted, the goods imported by the recordant or their designee, written consent from the recordant, or the one item personal exemption under 19 CFR 148.55 for foreign made goods carrying a recorded trademark. Section 133.22(d) then closes the first door for counterfeits specifically, so the removal path is not general purpose.

Baggage and postal arrivals get their own treatment in 19 CFR 133.24, where the 30 day period starts from the notice that the restrictions apply rather than from examination, noncommercial mail and commercial mail at $250 or less receives notice on CBP Form 8, and the importer or addressee may ask for exportation or destruction instead of waiting.

The disposition rules in 19 CFR 133.52 finish the picture. After a forfeiture, goods are handled by obliteration and then delivered to a government agency with an established need, gifted to a qualifying charitable institution, or sold at public auction once more than 90 days have passed since forfeiture without such a need being established. Forfeited copyright articles are destroyed except where 133.42(g) or 133.47(g) provides otherwise. A workflow that models forfeited as one status has nothing to show for these branches.

The part a fulfillment system can own

None of the above is a warehouse task. No member of a fulfillment team decides whether a mark is substantially indistinguishable from a registered one, files a response inside a business day window, or negotiates with a rights holder.

What the operator can produce is the dated record. FulfillNexa by SBT (fulfillnexa.com) supplies that layer from three Chinese facilities, one of them a Suzhou building of 13,000 square meters, and what leaves our site for a disputed shipment is a set of frozen facts: what was picked, what was packed, how the goods and their packaging were photographed, what description and value went to the shipping channel, and on what dates. Those fields are the raw material for the seven business day answer, and they are also the fields CBP can describe to somebody else from entry paperwork and manifests.

Build the snapshot before the letter arrives, and the clocks stop being surprises. That is the whole argument for treating a detention as a state machine rather than an email you will deal with later.

Top comments (0)