MSC and ASC Trademark Rules: B2B Acronyms vs MSCI Licensing

What the trademark requirement is, and why it exists

Seafood certification integrity depends on the strict control of intellectual property rights and certified claims. Quality managers, compliance leads, and internal auditors must distinguish between business-to-business product identification exemptions and mandatory licensing rules for consumer-facing materials. Under Section 4.9 of the MSC General Certification Requirements v2.6, the Marine Stewardship Council owns the MSC ecolabel, the name Marine Stewardship Council, and the acronym MSC, while the Aquaculture Stewardship Council owns the ASC logo, the name Aquaculture Stewardship Council, and the acronym ASC.

Marine Stewardship Council International operates as the dedicated licensing function managing trademark usage across both certification schemes. Under Clause 2.4 of the MSC Chain of Custody Standard: Default Version v5.1 and Group Version v2.1, organisations may only promote products as certified or apply logos if granted explicit approval under an MSCI licence agreement. This governance structure prevents misleading consumer claims, safeguards brand equity, and ensures that certified claims on consumer packaging map directly to verified, unbroken chain of custody supply chains.

B2B acronym exemptions versus MSCI licence requirements

The standard differentiates between internal operational traceability and external marketing claims. Under Clause 4.9.3.1 of the MSC General Certification Requirements v2.6 and Guidance 2.4 of the Default Standard v5.1, organisations may use the acronyms MSC or ASC and full scheme names without an MSCI licence agreement when operating strictly within a business-to-business, non-consumer facing context. Permitted unlicensed uses include physical product identification on processing totes, storage pallets, internal movement logs, delivery notes, shipping cartons, and line items on B2B sales invoices under Clause 2.2.

Conversely, any trademark application visible to final consumers or used for commercial promotion requires a formal licence agreement. Under Clause 4.9.3 of the General Certification Requirements v2.6, any entity placing MSC or ASC logos, names, or acronyms on consumer-ready packaging, restaurant menus, retail fish counter tags, or promotional marketing collateral must hold an active MSCI licence. Furthermore, applicants for certification may use scheme names and acronyms without a licence solely to inform stakeholders about audit schedules and solicit stakeholder feedback under Clause 4.9.3.2.

Audit verification protocols, non-conformities, and enforcement

Auditors evaluate trademark compliance during annual surveillance and recertification audits. Under Clause 8.2.14 and Clause 8.3.15 of the MSC Chain of Custody Certification Requirements v3.2, the auditor must verify that labelled products are covered by an active MSCI licence agreement and inspect documented MSCI artwork approvals for a sample of packaging designs or menus. Under Clause 7.1.8, the auditor verifies licence status on the scheme database or requests written confirmation from MSCI at ecolabel@msc.org when a third-party customer holds the licence.

If an organisation uses trademarks on consumer packaging or promotes products as certified without an active licence agreement, the auditor must enforce strict contractual remedies. Under Clause 4.9.5.1 of the General Certification Requirements v2.6, the Conformity Assessment Body shall raise a non-conformity and instruct the client to cease trademark usage and certified sales immediately. Under Clause 4.9.5.2, the CAB must transmit a copy of the non-conformity notice to MSCI within seven calendar days.

Step-by-step procedure for managing trademark approvals and B2B claims

• Review proposed trademark usage to determine whether the application is non-consumer facing B2B identification or consumer-facing promotion.
• Apply acronyms MSC or ASC to B2B delivery notes, invoices, and storage labels without an MSCI licence under Guidance 2.2 and Guidance 2.4.
• Submit an application to MSCI at ecolabel@msc.org to obtain an MSCI Licence Agreement prior to designing consumer packaging or promotional materials.
• Submit all draft packaging artwork, retail display designs, and restaurant menus to MSCI for formal review and written approval before printing.
• Archive MSCI design approval emails alongside corresponding artwork files to demonstrate compliance during annual CAB audits under Clause 8.2.14.b.

Example

A seafood smoking facility holding Default Standard certification prepares to launch a retail line of packaged smoked trout featuring the ASC logo. The quality manager verifies that B2B raw material invoices received from the fish farm utilise the ASC acronym under Guidance 2.2 without requiring a licence. Before printing retail bags, the company executes an MSCI Licence Agreement under Clause 2.4 and submits draft artwork to MSCI for formal sign-off. After receiving written packaging approval from MSCI, the plant commences production and files the approval email in its audit repository, enabling the auditor to confirm compliance under Clause 8.2.14.

Before your audit

• Verify that all B2B sales invoices and delivery notes identify certified items using approved acronyms or CoC codes under Clause 2.2.
• Confirm that an active MSCI Licence Agreement is in place for all consumer-facing labelled products under Clause 2.4.
• Compile written MSCI packaging design approval emails for all active retail SKUs and menus under Clause 8.2.14.b.
• Verify that a signed Seaweed Partnership Agreement is executed prior to handling certified seaweed under Clause 4.9.4.
• Confirm that third-party licence holders are verified in writing with MSCI if packing under private customer labels under Clause 7.1.8.
• Ensure that non-certified seafood ingredient calculations comply with MSCI percentage limits for multi-ingredient items.
• Audit warehouse storage areas to confirm physical totes and pallets display clear B2B acronym identifiers under Clause 2.1.

Questions people ask

Can a seafood processor use MSC acronyms on B2B invoices without paying an MSCI licence fee?

Yes, under Clause 4.9.3.1 of the MSC General Certification Requirements v2.6 and Guidance 2.4 of Default Standard v5.1, organisations may use the acronyms MSC or ASC on B2B traceability records, storage labels, and sales invoices without a licence agreement or royalty fees. This exemption applies strictly to non-consumer facing transactions between certified supply chain entities.

What happens if an organisation prints the MSC logo on consumer packaging without MSCI approval?

Under Clause 4.9.5.1 of the MSC General Certification Requirements v2.6, the certification body must raise a non-conformity, instruct the client to immediately cease using the trademark, and notify MSCI within seven calendar days. The client must halt sales of the unapproved packaging until formal written approval is granted.

Is a separate trademark agreement required for business-to-business trading of certified seaweed?

Yes, under Clause 4.9.4 of the MSC General Certification Requirements v2.6, any party intending to handle ASC-MSC seaweed must execute a Seaweed Partnership Agreement before using trademarks, even in a non-consumer facing B2B context. This requirement overrides the standard B2B acronym exemption applicable to wild fish and farmed seafood.

How does an auditor verify trademark authorisation during a Chain of Custody audit?

Under Clause 8.2.14 and Clause 8.3.15 of the MSC Chain of Custody Certification Requirements v3.2, the auditor verifies that the client holds an active MSCI licence on the scheme database and inspects written MSCI packaging approval proofs for a sample of labelled products. If a third-party customer holds the licence, the auditor seeks written confirmation directly from MSCI.

Reference documents

• MSC Chain of Custody Standard: Default Version v5.1
• MSC Chain of Custody Standard: Group Version v2.1
• MSC Chain of Custody Certification Requirements v3.2
• MSC General Certification Requirements v2.6
• ASC Chain of Custody Module v1.1