A blank disclosure policy for marketplace sellers, from identity to corrections

A marketplace seller software disclosure policy should tell a reader who is speaking, what relationship exists, which evidence supports a claim and what remains uncertain. It does not cure an unsupported product statement, hidden charge, missing safety record or unlawful data use.

This blank template was researched on 6 September 2026 for one England merchant and named marketplace account. Every factual value, party and channel remains for the buyer to complete and for qualified reviewers to approve.

Policy ownership and scope

Field	Buyer entry
Seller legal entity and contact	[enter verified seller]
Marketplace and account	[enter authorised account]
Software service and edition	[enter contracted service]
Policy owner and approvers	[enter named roles]
Products, audience and territories	[enter bounded scope]
Version, effective date and recheck	[enter approved record]

Keep the seller, marketplace operator, software supplier, managed provider, advertiser and payment or fulfilment party distinct. A marketplace badge or technical connection does not show which entity contracts with the consumer.

Label the communication and relationship

For each placement, enter one class: approved seller product fact, editorial material, seller advertising, paid marketplace promotion, affiliate content, sponsorship, customer review or supplier statement. Add the payer, benefit, control over content, placement owner and evidence expiry.

The CAP Code says non-broadcast marketing communications must be obviously identifiable in its recognition rules. CAP's July 2026 testimonials and endorsements advice covers genuineness, evidence and material commercial interests, while stating that it is not legal advice. The advertising and consumer reviewers must assess the actual context.

Attach product, price and limitation fields

Every product statement needs exact wording, model or population, source, evidence owner, access date, limits and withdrawal trigger. Product-safety statements also need role, traceability and applicable-regime review. OPSS business guidance distinguishes Great Britain and Northern Ireland and notes that sector rules may apply.

For price, enter currency, VAT treatment, mandatory charges, optional amounts, delivery and valid period. Link the invitation to purchase to the resulting order record. The CMA's price-transparency guidance addresses mandatory charges and pricing presentation. Leave every value blank until verified.

Explain data and automated activity

List personal-data purposes, recipients and retention beside the relevant journey. Name any cookie, pixel, SDK or other device storage or access, its purpose, duration and responsible parties. The ICO's final April 2026 storage and access guidance supplies the current PECR boundary.

If automated or inferred output affects listing, price, stock, fraud handling or customer treatment, describe the input, purpose, human owner, contest route, material limits and rollback. Do not call supplier marketing evidence of accuracy, fairness or legal permission.

Place and test the disclosure

State where the disclosure appears, when a person sees it, the wording owner and the accessible alternative. Test it in the actual listing, advert, review and customer journey. A footer link may be too late for a material relationship or limitation; a qualified reviewer decides placement.

Correct without concealing the old record

Give readers and staff a correction route. Preserve the previous claim, source, change reason, authoriser, affected channels and completion evidence. Set triggers for expired proof, product incident, price change, relationship change, regulator update or failed tracking control.

This draft stays on publication hold. The final policy needs named advertising, consumer, safety, privacy, accessibility and contract approval for the exact facts and date.