When bulk fertilizer is filled into big bags at a port, the terminal creates transport units but does not become the manufacturer or regulatory owner of the product label. The importer must supply approved label data and a batch-control rule that connects each filled unit to the correct product, shipment and documents.
A label is not merely branding. Depending on the destination and product, it may carry legally required product, safety, quantity, operator and traceability information. The responsible market party must identify the applicable rules before printing starts.
Separate packaging marks from product labels
An FIBC may carry information from the packaging manufacturer, such as:
- packaging identity;
- rated safe working load;
- design or test information;
- handling pictograms;
- single-trip or reusable status;
- manufacturer traceability.
The product label may separately include:
- commercial product name;
- responsible manufacturer or importer details;
- product composition or declared properties;
- net quantity;
- batch, lot or other traceability reference;
- instructions and warnings required for the market;
- language required at destination;
- customer or distribution references.
Do not cover, contradict or replace packaging-manufacturer information without approval from the responsible packaging specialist.
Assign label ownership
Before bagging, record who is responsible for:
- determining legally required product information;
- approving translations;
- approving artwork and print proof;
- supplying variable batch and quantity data;
- confirming the link between label and declaration;
- releasing the label version for production;
- authorizing correction or replacement;
- retaining the approved master file.
The terminal should apply the released instruction and record its use. It should not draft claims, select a commodity classification or decide whether the label makes the product market-compliant.
Market rules depend on destination
For example, EU Regulation 2019/1009 requires EU fertilising products to carry identification such as a type or batch number and specifies responsibilities for manufacturers and importers. Updated EU rules also allow certain digital-label structures under defined conditions.
Those EU requirements apply only when the product and placing-on-the-market scenario fall within their scope. They are not a substitute for Ukrainian rules or the requirements of another destination. The importer must obtain current regulatory advice for the actual market.
Build a label version-control process
Use a controlled sequence:
- importer supplies approved master data;
- artwork is generated from that data;
- responsible party approves a proof;
- the approved version receives an identifier and release date;
- obsolete versions are blocked from use;
- variable data are generated under an agreed rule;
- the terminal records which version and range were applied;
- unused, damaged or superseded labels are reconciled.
Email filenames such as final-v2-new.pdf are not reliable version control. Use a clear approval identifier.
Define the batch before filling
The batch reference may follow the manufacturer lot, vessel parcel, storage lot, filling run, customer allocation or another approved logic. These are not automatically the same.
Agree:
- what event opens a new batch;
- whether supplier lots may be combined;
- how storage identity carries into filling;
- whether a filling interruption changes the batch;
- how rebagged units are referenced;
- how customer-specific allocations are recorded;
- which batch appears on customs, survey and dispatch records.
If one vessel parcel is divided among several buyers, the commercial allocation can be separate from the underlying product batch. The records should preserve both relationships.
Control variable information
Variable fields may include batch, unit number, target or actual quantity, filling date, customer reference or destination. Decide which values are printed, which are stored electronically and which appear in the packing report.
The process should prevent:
- duplicate unit numbers;
- labels from the wrong product or customer;
- a new label version entering mid-run without recorded changeover;
- units leaving before label verification;
- manual corrections without approval;
- labels becoming unreadable during storage or handling.
Handle non-conforming units
Define what happens when:
- the bag is damaged;
- the label is missing, unreadable or incorrect;
- quantity is outside the agreed tolerance;
- product identity is uncertain;
- a unit is rebagged;
- customer allocation changes after filling.
Typical control statuses may include hold, relabel, rebag, recheck or release. The responsible cargo party authorizes product disposition; the terminal records the physical action it performs.
Reconcile the filling run
The final report should connect:
- bulk quantity presented for filling;
- number of units filled;
- quantity basis;
- packaging and label versions used;
- batch and unit-number ranges;
- unused or rejected bags and labels;
- held, rebagged or relabeled units;
- samples and survey attendance;
- quantity remaining in bulk or process interfaces;
- lots released to storage or dispatch.
Information for the terminal
Provide the approved FIBC specification, packaging instructions, label master, version identifier, variable-data logic, batch rule, quantity tolerance, non-conformance process, survey requirements and final report format.
Where label application or batch reporting is requested as part of an FIBC filling project, the available scope is confirmed directly before operations. The importer or other responsible product party remains accountable for regulatory content and market compliance.