For a feed manufacturer or importer, a Certificate of Analysis (COA) is often the first technical document requested from a sodium bicarbonate supplier. It should be important, but it should not be treated as a complete supplier approval. A COA is a batch-specific statement of analysed characteristics against a stated specification. It can establish what was tested and reported for a defined lot. It cannot, by itself, prove that the material will flow through a particular dosing system, blend uniformly in a particular formulation, remain suitable after a particular logistics route or meet every requirement in the buyer’s destination market.

The strongest sourcing decision therefore uses the COA as evidence inside a wider control system: an agreed purchase specification, a technical data sheet (TDS), an SDS, traceable labelling, receiving checks, appropriate storage, change control and a representative qualification trial where the customer’s process requires one. This approach is more rigorous than accepting a generic statement of ‘feed grade’ and more useful than requesting an unnecessarily long list of tests without knowing what decision each result will support.

Start with the right question: what does the COA need to prove?

Before comparing supplier documents, the buyer should convert the intended use into a written acceptance specification. That specification should identify the material as sodium bicarbonate (NaHCO3), define the grade and approved use, state the chemical and physical controls relevant to the feed-mill process, and name the destination-market, customer or certification requirements that apply. The supplier’s COA should then be read against that agreed specification – not against an assumed global standard or a competitor’s unrelated grade.

What a batch-specific COA can support	What the technical team should clarify
Batch identity and the date or reference of analysis	Fitness for every feed formulation, dosing system or storage environment
Reported chemical and physical test results against stated limits	Uniform mixing performance unless that is qualified in the buyer’s process
Comparison of one production lot with the approved purchase specification	Compliance with every country-specific import, labelling or feed-use rule
Traceability when it is linked to labels, shipment records and retained samples	A complete assessment of supplier change control, transport condition or customer approval

1. Confirm material identity and lot traceability

Begin with the identifiers, not the numbers. The document should clearly identify the product as sodium bicarbonate and link the COA to one defined batch or lot. The same identifier should be recoverable on the bag, pallet or other agreed shipping label, as well as on the packing list and delivery documentation. The document should also make the product grade and intended application clear enough to avoid a local, regional or another sodium bicarbonate grade being released into a feed-material process without formal approval.

A reliable traceability chain is practical rather than decorative: a receiving team should be able to start with a bag or pallet code, find the corresponding lot and shipment, and identify the relevant production and customer records. If the buyer operates retained samples, the sample label should use the same lot reference. A COA that cannot be linked to physical product is not a valid release document.

• Product name and chemical identity: sodium bicarbonate / NaHCO3, with the supplier’s grade designation clearly shown.
• Batch or lot number: unique, legible and consistent across the COA, packaging and shipping documents.
• Production, analysis and release references: dates and document versioning should support the buyer’s record system.
• Supplier and manufacturing-site identity: sufficient to support the buyer’s approved-supplier and change-control processes.
• Traceability link: a clear route from the received unit to the batch-specific COA and any retained sample record.

2. Read the result, specification, unit and method together

A COA is most useful when every reported parameter is presented with four connected elements: the agreed specification, the actual result, the unit of measure and the test method or analytical reference. The word ‘pass’ is not a replacement for these elements. Nor is a result comparable when one supplier reports a percentage, another reports mg/kg and neither identifies the analytical basis. The buyer’s quality team should establish, before routine supply, which format and methods are acceptable for its programme.

Where a parameter is important to product performance or regulatory acceptance, ask whether the limit refers to the received material, a dry basis, a specified particle fraction or another defined basis. The intended purchase specification should settle this question. This is especially important when results are rounded, when a calculation is reported instead of a direct test, or when an external laboratory and the manufacturer use different reporting conventions.

3. Treat chemical compliance and feed-mill performance as separate checks

Sodium bicarbonate is a defined chemical substance, but the buyer’s operating question is broader than chemical identity. Two lots may both meet an agreed chemical limit and still require different attention in receipt, storage or blending if their physical attributes, packaging condition or handling history have not been qualified for the customer’s process. This does not mean that one lot is necessarily non-conforming; it means that chemical conformance and operational suitability should not be confused.

For this reason, particle size, moisture-related condition and packaging integrity should be discussed in the same qualification meeting as the COA. The buyer should define the actual addition point, the type of mixer, dust-control expectations, storage residence time, warehouse climate and sampling approach. A supplier can then state which information it routinely controls and which conditions are best confirmed in the buyer’s own trial.

4. Verify risk-based contaminant and documentation controls

The appropriate contaminant profile is not universal. It depends on the material’s supply chain, manufacturing process, target species, destination market, customer requirements and the buyer’s documented risk assessment. Where the buyer has a regulatory or customer-driven limit, the COA or supporting test report should show a meaningful result, unit and method. A generic statement that a product is ‘free from’ a substance is not a substitute for a defined specification and appropriate evidence.

The same logic applies to the documentation set. A batch-specific COA is normally read with the TDS and SDS. The TDS states the intended technical characteristics and handling information; the SDS communicates relevant safety and transport information; the COA reports the particular batch result. For imports or customer-approved programmes, a certificate of origin, quality-system evidence, declarations or other market-specific documents may also be needed. The document pack should be agreed before dispatch, not reconstructed after a container has arrived.

5. Look for signals that require clarification before release

A discrepancy is not proof of poor quality, but it is a reason to pause and obtain a clear explanation. Procurement should not force a quality release merely to protect a delivery date. The right response is to compare the material and documents against the approved specification, record the query and close it through the supplier’s documented response or the buyer’s deviation process.

• The batch number on the COA cannot be matched to the received product, packing list or shipping paperwork.
• Results are reported only as ‘pass’ or ‘conforms’, without an agreed specification, unit or analytical method where those details are required.
• The grade, intended use, manufacturing site or packaging differs from the approved supplier record without prior change notification.
• A parameter critical to the buyer’s process is absent, reported on an unclear basis or shown with an unapproved method.
• The COA is not clearly batch-specific, is incomplete, or contains unexplained corrections, conflicting data or document-version uncertainty.
• The packaging is damaged, wet, contaminated or inconsistently labelled, even if the COA itself appears acceptable.

A practical release workflow for the receiving team

The precise workflow should reflect the buyer’s food/feed-safety system, but the release decision is strongest when procurement, quality and operations each see the same evidence. The following sequence separates paperwork review from the physical and operational checks that paperwork cannot replace.

1. Approve the written purchase specification. Define product identity, grade, critical parameters, reporting basis, documentation and applicable market requirements before purchase order release.
2. Verify the pre-dispatch document pack. Review the TDS, SDS, draft or batch-specific COA and any import/customer documents against the approved specification.
3. Inspect receipt condition. Check package integrity, label legibility, lot identity, quantity and any signs of moisture exposure, contamination or damage.
4. Match physical units to documents. Confirm that the lot references on bags, pallets and transport records correspond to the exact COA being released.
5. Decide whether sampling or a qualification trial is required. Use the buyer’s documented plan, risk assessment and acceptance criteria; do not use ad hoc testing as a substitute for a specification.
6. Record disposition and change control. Release, hold or reject through the buyer’s quality process, retain the evidence, and assess any supplier or process change before routine use.

Why the COA belongs in a supplier-qualification system

For feed ingredients, safe sourcing and traceability are supply-chain responsibilities, not merely document requests. Codex and feed-hygiene frameworks emphasise safe sources, risk-based controls and the ability to trace materials through the chain. In the United States, sodium bicarbonate is recognised as safe for animal-feed use when used in accordance with good manufacturing or feeding practice. That status does not prescribe a universal quality specification, use level or performance claim. It reinforces the need for a purchaser to control the intended use and evidence relevant to its own programme.

The commercial benefit is straightforward: a buyer who defines its requirements early can compare suppliers on a common technical basis, receive a more usable document pack, and reduce the risk of a shipment being held because the lot cannot be verified. A supplier who provides clear batch evidence and responds transparently to technical questions becomes easier to qualify for repeat business.

A better COA conversation with Fajara

Fajara can provide the Feed Grade Sodium Bicarbonate TDS, a representative or batch-specific COA and product information to support the buyer’s qualification process. The buyer should share the required specification, destination market, feed-mill handling conditions and documentation needs at the start of the enquiry. This enables a focused technical discussion about the product, batch evidence and the appropriate qualification route – without making unsupported claims about a final feed or animal outcome.

Regulatory and responsible-use note

Regulatory status, documentation and product classification must be confirmed for the destination market and intended use. In the United States, 21 CFR 582.1736 identifies sodium bicarbonate as generally recognised as safe when used in accordance with good manufacturing or feeding practice. European feed-hygiene requirements also address traceability and feed-business responsibilities across the chain. These references do not replace local law, customer specifications, import requirements, nutritional advice or a buyer’s own risk assessment. This article is educational information, not legal, regulatory or nutritional advice.

Technical sources and further reading

• eCFR, 21 CFR 582.1736 – Sodium bicarbonate – United States feed-use reference.
• Codex Alimentarius, CXC 2004-54: Code of Practice on Good Animal Feeding – Safe sourcing and risk-based feed controls.
• FAO and IFIF (2010), Good Practices for the Feed Industry – Guidance on feed safety, storage, transport and analysis.
• EUR-Lex, Regulation (EC) No 2008/183 on feed hygiene – Feed-hygiene and traceability framework.
• FDA, Preventive Controls for Animal Food – Documentation and verification content for covered facilities.