PIM for chemicals: identifiers, packs and documents
Organise chemical identifiers, pack units and source documents in PIM, keeping catalogue publication separate from use and safety decisions.
- Published
- Last updated
PIM for chemicals keeps the supplied product identity, pack quantity and applicable documents together in each published catalogue record. Product information management (PIM) helps your team approve that information and send it consistently to sales channels. The product name alone cannot establish which formulation, container or document a customer is viewing.
Start with the exact orderable product and work back to its manufacturer’s records. Keep catalogue publication separate from chemical classification, handling and permissible-use decisions. The controls below concern the information your merchant catalogue publishes, within the wider PIM industry guides.
Identify the exact chemical product record
Separate the trade name, manufacturer’s product identifier and orderable pack record before you import descriptions. A shared name can cover several packs, while a similarly named variant can require different supporting documents.
Give each orderable pack an internal stock keeping unit (SKU). Retain the supplier code and manufacturer’s code in separate fields. Record formulation or grade distinctions exactly as the source supplies them, and keep the source reference with the value. A catalogue editor must not infer a classification from the product category or a word in its name.
DIGGERS Methylated Spirits illustrates the different identity levels. Its manufacturer’s product data sheet lists pack codes including 15000-61DIG and 15000-4DIG. It also distinguishes unit barcodes from carton barcodes. The linked safety data sheet uses manufacturer’s product code 15000. Those identifiers have different jobs and need separate fields.
Keep a product family above its packs when the supplier evidence supports shared information. Attach a document at that level only when its applicability covers every child record. A new variant needs an explicit document match before it inherits a family’s public link.
Chemical ingredient identifiers also need their own meaning. An ingredient identifier copied from a safety data sheet does not, by itself, identify the merchant’s packaged formulation. Preserve the supplier’s product identity and the commercial pack relationship instead of merging records because one ingredient matches.
Control units and source documents
Store pack contents, order quantity and document applicability as separate values. A customer ordering one carton needs to know both the number of containers and the contents of each container.
Chemical catalogue controls
| Record area | Required information | Check before publication |
|---|---|---|
| Supplied product | Trade name, maker identifier and documented variant | Match the supplier record to the exact product |
| Orderable pack | Merchant SKU, supplier pack code and selling unit | Keep a carton distinct from an individual container |
| Contents | Container count, quantity per container and unit | Publish enough detail to interpret one ordered unit |
| Barcodes | Unit and carton identifiers in separate fields | Map each barcode to the packaging level it identifies |
| Safety data sheet | Issuer, product identifier, revision and market applicability | Confirm that the document covers this supplied product |
| Technical document | Document type, version and applicable variants | Avoid substituting a technical sheet for a safety data sheet |
| Approval | Responsible reviewer and approved source version | Keep an imported replacement pending until reviewed |
A safety data sheet (SDS) has a defined identification section. Safe Work Australia’s SDS guidance describes that section and the duties to keep SDS information current. Use the product identifier to help match the document. Keep its review and issue dates in your document record so the responsible person can manage replacement.
The DIGGERS safety data sheet identifies its product, manufacturer’s code and issue number. Its product data sheet separately lists commercial pack information. Preserve both document types with their own versions. Replacing one does not establish that the other has changed.
Store the original document or a versioned reference alongside the public URL. A working link only proves that a file is available. Check the file’s product identifier and applicability before approving it for a particular catalogue record.
Treat a missing source as an unresolved data issue. Route document questions to the supplier or the person responsible for product compliance. Keep chemical classifications and use decisions with that responsible person, outside automatic category or keyword rules.
Check the published catalogue record
Follow a supplier revision through approval and inspect the page and exported data customers receive. Use the following fictional example to define the expected results.
A merchant sells fictional product CL-20 as SKU CL20-5. The approved pack is one 5 L container. Supplier document revision R2 applies to that product, and the storefront links to its approved SDS. The supplier then sends revision R3 and an updated packaging file.
- Match the update using the supplier’s product and pack codes. Keep R2 in the history while R3 enters review.
- Have the responsible reviewer check R3’s product identity and applicability. Record the decision before replacing the active document reference.
- Compare the packaging file with the approved 5 L record. If it describes a different pack, keep it separate until the supplier resolves the identity.
- Publish the approved change and inspect the storefront download. Open the file itself, then compare its revision with the approved PIM record and channel export.
Test a stale SDS by leaving one channel pointed at R2 after R3 is approved. The check must find that channel’s old reference. Correct the destination mapping or cached asset, then open the customer-facing download again.
For a wrong-pack case, send a carton quantity into the field intended for container volume. The expected result is a review exception, with the existing approved pack preserved. A numeric value passing validation is insufficient when its meaning has changed.
Finally, remove the source document from an incoming row. An empty cell must not silently erase the approved reference or mark an unsupported replacement ready to publish. Define whether blanks mean no change or an explicit removal, and require approval for removal where a document is required.
Assess ownership and PIM integration
Assess a PIM by how it controls supplier changes and resolves exceptions across every publication route. Compare the work needed to maintain approved records as well as the initial import.
Akeneo’s import documentation distinguishes skipping an invalid row from importing its valid values while skipping an invalid value. It also describes import permissions and changes to product associations or status. Include those paths when evaluating restricted editing. A locked editing screen alone does not establish the behaviour of imports.
Assign ownership field by field. Enterprise resource planning (ERP) software can own orderable pack codes and stock, while PIM owns approved descriptions and document references. Define which system controls selling units, how conflicts are raised and who approves a changed pack mapping.
For each channel, document the connection method and the fields it sends. A file export, an official connector and a custom integration have different operating tasks. Check the actual pack and document fields instead of accepting a general claim that the systems integrate.
Give exceptions a named owner and a resolution state. Supplier document changes need a review route, while mapping errors need a channel owner. Before choosing a workflow, run the fictional revision through both routes and confirm that the approved pack and document survive the next routine stock update.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.