Documentation Index
Fetch the complete documentation index at: https://docs.closient.com/llms.txt
Use this file to discover all available pages before exploring further.
US states are starting to mandate per-product ingredient and safety disclosure tied to scannable codes on the package. Louisiana (SB 14, Act 463 of 2025) and Texas (SB 25 of 2025) are the first two; California, New York, Illinois, and others have similar bills in flight. The pattern is the same in every draft:
- A defined list of ingredients (preservatives, dyes, additives) that triggers the obligation if present in a covered food product.
- A requirement that the package carry a scannable code (QR or other machine-readable identifier).
- A requirement that the code resolve to a web page disclosing the regulated ingredient and, in most drafts, accompanying safety information.
Closient is built for this pattern. Every product in the catalog already has a GS1 Digital Link resolver entry; surfacing the disclosure is a matter of registering one extra link type (gs1:ingredientsInfo, gs1:safetyInfo) and pointing it at content the brand controls. No new domain, no new infrastructure, no migration.
This section explains how Closient satisfies each law, why our resolver-based architecture is the right substrate for the copycat wave, and what you as a brand operator need to do to flip disclosure on for a product.
Not legal advice. This documentation is provided for engineering and operations teams implementing against Closient. It is not a substitute for review by qualified counsel licensed in your jurisdiction. Statutory text, effective dates, and enforcement posture change; verify against the official bill text before relying on any specific claim below.
The two laws at a glance
| Law | Bill | Effective | Covered products | Disclosure surface |
|---|
| Louisiana SB 14 (Act 463 of 2025) | LA SB 14 | Labeling rules: January 1, 2028 | Food and beverage manufactured on or after the effective date, sold for human consumption in Louisiana, containing one or more of 44 listed ingredients | QR code on the package linking to a web page under manufacturer control |
| Texas SB 25 (89R SB 25) | TX SB 25 | Labeling rules: January 1, 2027 (statute effective Sep 1, 2025) | Food product offered for retail sale in Texas, containing one or more of 44 listed ingredients | URL, QR code, barcode, or other electronic means linking to required disclosure |
| LA SB 14 | TX SB 25 |
|---|
| Detail page | Louisiana SB 14 | Texas SB 25 |
| Ingredients in list | 44 | 44 |
| Effective for labels | Jan 1, 2028 | Jan 1, 2027 |
| Enforcement | Attorney General (LA R.S. 51:1407 et seq. — unfair trade practice) | Department of State Health Services |
| Exemptions | Drugs, dietary supplements, alcoholic beverages, retail-prepared food, medical foods | Drugs, dietary supplements, alcoholic beverages, retail-prepared food, medical foods, USDA-regulated meat and poultry |
How Closient satisfies the disclosure obligation
Three building blocks, all of which Closient ships out of the box:
1. GS1 Digital Link resolver as the scannable target
Every product in Closient already has a resolver URL of the form:
https://www.closient.com/01/{gtin}
2. Link types as the disclosure routing primitive
The GS1 Web Vocabulary defines link types — semantic tags that say what a particular destination URL contains. The two relevant link types for state ingredient disclosure are:
| Link type | GS1 IRI | Purpose |
|---|
gs1:ingredientsInfo | https://gs1.org/voc/ingredientsInfo | The “what is in this product” disclosure page |
gs1:safetyInfo | https://gs1.org/voc/safetyInfo | The accompanying safety/warning information page |
linkType query parameter or content negotiation. The Louisiana and Texas statutes both specify that the linked page must surface the regulated ingredient and (Louisiana) accompanying safety information; mapping each obligation to a distinct link type keeps the semantics clean and lets the brand update the safety surface independently of the ingredient surface.
See the GS1 link type vocabulary for the full registry.
3. Manufacturer-controlled content via resolver rules
LA SB 14 R.S. 40:661(B)(2) requires that the QR resolve to “a web page that is under the control of the manufacturer.” The Texas statute uses similar manufacturer-control language. Closient interprets this as functional editorial control, not infrastructure ownership — see Manufacturer Control for the full architectural rationale, including why this reading is correct under both the US state statutes and the EU Digital Product Passport regime.
The practical mechanism: every brand has a resolver rule configuration in their Closient dashboard. To flip ingredient disclosure on for a product, add a rule that maps the gs1:ingredientsInfo link type to a page the brand has authored — either a Closient-hosted page (the default; brand edits the content via the dashboard) or a custom URL on a domain the brand operates.
Configuration example
Enabling LA SB 14 / TX SB 25 disclosure for a product is a single resolver-rule addition. Via the Products API:
curl -X POST https://www.closient.com/v1/products/{gtin}/resolver-rules \
-H "X-API-Key: $CLOSIENT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"link_type": "gs1:ingredientsInfo",
"destination_type": "HOSTED_PAGE",
"hosted_page_id": "page_01HXYZ...",
"scope": "PRODUCT"
}'
hosted_page_id references the disclosure page the brand has authored in the Closient dashboard. For brands who already have an ingredient-disclosure surface on their own infrastructure, swap destination_type to CUSTOM_URL and supply the target URL plus a fallback policy — the resolver monitors custom URL health and can fall back to the Closient-hosted page automatically if your domain becomes unreachable.
Repeat for gs1:safetyInfo to surface the accompanying safety information page that LA SB 14 R.S. 40:661(B)(3) requires.
Why this approach scales to copycat laws
The copycat wave that LA SB 14 and TX SB 25 are kicking off will follow the same pattern: a state-specific ingredient list, an effective date, an exemption carve-out, and a “QR/scannable code on the package linking to manufacturer-controlled disclosure” mechanism. Building one disclosure surface per state is the wrong architecture — the brand ends up with five QR codes on a single product and a different domain for each.
Closient’s resolver inverts the problem: one QR code per product, one resolver endpoint, content routed by link type and locale. When a new state law lands, you do not re-print the package. You register one additional link type or one additional locale variant and the existing QR resolves correctly in that jurisdiction. The same architecture is what makes Closient the natural fit for the EU Digital Product Passport — see Manufacturer Control for the convergence argument.
Not legal advice. Verify all statutory references, effective dates, and ingredient lists against the official bill text. Consult counsel licensed in the relevant jurisdiction before relying on the configuration described above for regulatory compliance.
