Build and review a product label

What you will accomplish

You will choose a reusable layout, connect the correct formula or batch context, generate a label record, and review its source freshness and output. Formuley organizes release copy, snapshots, barcodes, and QR data; it does not decide that the artwork is legally sufficient or safe to release.

Before you start

The label generator, reusable templates, and barcode generation require Pro or higher. The custom label designer at /labels/designer requires Lab or higher. Confirm the intended product, SKU, formula version, batch when applicable, target markets, reviewed INCI snapshot, compliance snapshot, net contents, responsible-party details, directions, warnings, and traceability fields.

Open the label workspace

1. Open Labels. Go to /labels to review generated records, output types, approval state, and snapshot freshness.
2. Choose Generate from batch when the label is batch-specific. Select the intended record from /batches and review its release context.
3. Open a formula-scoped label view when appropriate. Use /labels?formula=[formulaId] from the formula's Release setup.
4. Resolve release blockers first. A label should use current reviewed formula, compliance, and INCI evidence rather than disconnected typed copy.

Choose or create a template

1. Open Templates. Go to /labels/templates to compare system and custom layouts, dimensions, content, ownership, and update time.
2. Choose a system template on Pro. Confirm its shape, millimeter dimensions, and included fields for the intended stock.
3. Choose New template only with Lab access. The custom designer supports rectangle, square, circle, oval, and custom shapes.
4. Set the reusable layout. Choose vertical, horizontal, or centered alignment; a supported typeface; and the brand, canvas, and text colors.
5. Select only supported fields. Available toggles include INCI, allergen callouts, net weight, expiry, batch number, country of origin, manufacturer, directions, warnings, and logo.
6. Choose machine-readable output when needed. Template options include Code128, EAN-13, UPC-A, QR, and DataMatrix, plus QR content for a URL, batch information, INCI list, or custom value.

Template controls arrange the supplied data. They do not verify code ownership, retail registration, legal field placement, minimum type size, language, net-contents rules, or market-specific copy.

Generate from reviewed source data

1. Confirm the release context. Check the product, default SKU, formula version, target markets, and review state.
2. Confirm the compliance snapshot. Rerun the intended market review when the formula, rules, product context, or evidence has changed.
3. Confirm the INCI snapshot. Generate a new declaration when the formula or ingredient identity has changed.
4. Select the intended template. Verify its dimensions and enabled fields before creating the label record.
5. Generate the draft label. Use the connected label action with the intended formula or batch and inspect the saved record in /labels.
6. Review the source status. A stale or blocked snapshot needs resolution before artwork approval.

Review the record and plan the artwork handoff

1. Inspect the generated record. Verify product name, INCI, allergen callouts, batch details, barcode or QR value, and approval state.
2. Compare the record with its source evidence. Confirm that the saved formula, INCI, compliance, and batch context are the intended versions.
3. Treat the workspace list as read-only. The current /labels table does not provide a PDF, SVG, or PNG download action.
4. Plan a developer handoff only when your organization uses the API. The authenticated developer API at /api/v1/labels/[id]/download can return PDF or SVG; this is not a native workspace download workflow and requires an implemented API integration.
5. Do not promise a PNG output. PNG is not currently available from the download service.
6. Complete artwork verification. A qualified regulatory reviewer must approve market copy, warnings, codes, dimensions, legibility, and final artwork before printing or release.

Check your work

• The label record belongs to the intended product, formula version, SKU, and batch.
• Its compliance snapshot and INCI snapshot are current and reviewed.
• The template has the correct dimensions, shape, fields, and code type.
• Every displayed value matches its verified source.
• The saved record has been inspected in the workspace, and any developer-API artwork handoff has been verified by the integration owner.
• A qualified regulatory reviewer and the appropriate release owner have approved the final artwork.

If something does not look right

• If New template is locked, custom layout controls require Lab; choose an available system template or upgrade through the normal plan workflow.
• If a label shows stale or blocked source status, refresh compliance and INCI evidence before generating another record.
• If a barcode or QR does not scan, verify the encoded value, code type, contrast, and physical size with the applicable external standard.
• If you expected a workspace download button, the current /labels table is read-only; coordinate an authenticated developer-API handoff when file output is required.
• If PNG was requested, plan a different artwork handoff; PNG is not currently produced by the download service.
• If a generated label looks complete but review evidence is missing, keep it in draft; label generation is screening and organization support, not release approval.

Next steps

• Generate and verify the INCI declaration
• Review the US and MoCRA screening
• Review the EU and allergen screening