That question cannot be answered by a folder labelled “certificates.” The business needs to know what was assessed, which physical units it describes, which market decision relied on it, and what the change leaves unresolved. A connected product record earns its place by preventing an unsupported sale while preserving the sales that still have a valid basis.
The shipment decision, not the document count
Fictional example: Fable sells an L1 table lamp with an external power adapter. The following lots, reports, reviews and quantities are invented for this decision exercise. They do not describe a certified product or an actual client engagement.
Lot A-01 contains 40 lamps with adapter A. Its prior market reviews separately cover 20 units allocated to the United States and 20 to Singapore. Those reviews have their own documented basis; they are not evidence that one country's permission transfers to another.
The supplier now proposes lot B-02: 100 lamps with adapter B, intended as 60 for the United States and 40 for Singapore. Its message says both adapters provide 12 V output. The report supplied with the old product expressly identifies adapter A; it does not list B as an assessed alternate. No qualified change assessment has yet established whether the old evidence applies to B.
The founder must decide whether to approve shipment and launch the new batch. “There are 140 lamps” is true. “There are 140 released lamps” has not been established.
Three options, with different consequences
Copying the old approval across the L1 product code is convenient, but removes the very distinction that needs review. The same nominal output does not, by itself, establish equivalent construction, protection, component suitability or coverage by the earlier assessment.
Stopping every Fable product in every market is also unsupported by these inputs. It may be appropriate if the change reveals a wider safety concern or the lots cannot be separated. Otherwise, it hides the actual scope and can interrupt unaffected business without resolving B.
The more useful choice is a scoped hold: identify B-02 physically and commercially, hold its release, and have the responsible specialist assess the change against each intended market. Reconfirm A-01's existing basis and separation rather than declaring it safe because it is older.
A completed disposition for this moment looks like this:
| Physical branch | Intended allocation | Evidence position | Commercial action now |
|---|---|---|---|
| A-01 / adapter A / United States | 20 | Prior US review exists; confirm it still applies and the change reveals no issue affecting A | Continue only under the still-valid prior release; do not substitute B into these orders |
| A-01 / adapter A / Singapore | 20 | Separate prior Singapore review exists; reconfirm scope and traceability | Continue only under that branch's still-valid release |
| B-02 / adapter B / United States | 60 | Old report names A only; B applicability unresolved | Hold release and customer delivery promise for this branch pending assessment |
| B-02 / adapter B / Singapore | 40 | B applicability and local component/product obligations unresolved | Hold release; obtain a separate Singapore disposition |
The table reconciles 40 old units plus 100 proposed new units. It deliberately does not invent a newly approved quantity. If A's prior release cannot be reconfirmed or units cannot be distinguished, its affected branch must also stop pending resolution. A spreadsheet label cannot overcome a mixed physical shipment.
Ask a question the supplier can answer with evidence
“Please send the certificate” encourages another attachment without establishing relevance. A useful request names the decision and missing coverage:
Fable L1, proposed lot B-02 — adapter substitution review
Our current report identifies adapter A. You propose adapter B for 100 units: 60 intended for the United States and 40 for Singapore. We have not released B-02.
Please supply the exact adapter manufacturer/model and specifications, the construction/change comparison against A, and the report or assessment showing whether B is an accepted alternate for this lamp configuration. Identify the report's product, component and destination scope; an adapter-only document must be labelled as such.
Confirm which units and packaging contain A or B, how B-02 will be kept separate, and whether any substitution has already occurred. We will obtain the relevant market review before authorising the affected release. Do not substitute B into A-01 orders.
This is finished request copy, not a claim that the supplier has responded. A real commercial team also needs an accountable reviewer, a purchase/dispatch hold that actually operates, and a record of the eventual decision. Emailing a question while automatic order routing continues does not hold a shipment.
Match each document to its scope
There is no universal “lamp certificate” that this example can safely prescribe. For US general-use products, CPSC's certification guidance ties certification to applicable consumer-product safety rules. That does not establish which rules cover this fictional lamp or that every lamp needs a General Certificate of Conformity.
For products actually within UL's certification programme, UL's Follow-Up Services explanation describes checking continued conformity with certified construction and components. That is a useful illustration of why substitutions matter within a defined programme. It is not a claim that Fable is UL certified, that UL is mandatory for every product, or that every change requires a complete new test programme.
Singapore provides a particularly useful boundary. The Consumer Product Safety Office's supplier FAQ explains that registration of an AC adapter used with another product covers the adapter, rather than the other product as well. An adapter's SAFETY Mark therefore cannot simply be presented as whole-lamp approval. The lamp, adapter, intended supply and applicable regime still need their own classification and assessment. This article does not classify the hypothetical lamp as a Controlled Good.
The practical question remains narrow: does this evidence cover this construction for this intended market and activity? The answer may differ between the adapter and lamp, and between destinations.
Keep product identity separate from permission to sell
The team might create an internal revision or lot distinction immediately to prevent substitution. That does not automatically answer whether the external trade item needs a new GTIN.
The GS1 GTIN Management Standard supplies change principles and specific rules for trade-item identity. Evaluate the actual change against the applicable rules and legal requirements. It does not follow that every routine adapter substitution always requires a new GTIN—or that keeping a GTIN unchanged proves the revised product can be supplied in every market.
A customer-facing SKU can remain familiar while the underlying assessed configuration changes. Equally, a newly assigned code does not make missing evidence valid. Keep enough identity to distinguish the physical units, then resolve the identification and release questions with their respective owners.
What would justify reopening B-02?
A qualified review might establish that B is already an acceptable documented alternate, that a targeted assessment or testing is needed, or that construction or supply plans must change. The outcome must name the covered configuration and market. Do not turn “US branch resolved” into “Singapore branch resolved,” or an adapter-only conclusion into a whole-product conclusion.
For the fictional case, release B-02 only after the relevant branch has a supported disposition, supplier units match that disposition, and the warehouse and selling offer can preserve it. If only 60 US-bound units are cleared, the other 40 remain unresolved. If B cannot be distinguished from A in the warehouse, sorting or other reliable control becomes part of the release work.
The recommendation changes when evidence exposes a problem shared by both configurations: the hold expands to the affected scope. It also changes when documented review supports B without additional testing: a blanket demand to repeat everything adds cost without necessarily adding evidence.
A useful product record therefore ends in a concrete permission and its limits. It tells purchasing what to accept, operations which units to dispatch, and the commercial team what it can promise. The number of uploaded documents is secondary to whether those three decisions agree.