All resources

Writing an internal compliance policy for a small RUO supplier

How a small research-use-only supplier can write a short compliance policy covering who it sells to, what it says, how orders are checked, who decides, how records are kept and when the policy is reviewed.

Illustration for Writing an internal compliance policy for a small RUO supplier

An internal compliance policy is a short written document that says how your business sells: who you sell to, what you say and do not say about your products, how orders are checked, who decides the hard cases, how records are kept and when the policy is reviewed. For a small research-use-only supplier, it can fit on a few pages.

Its value is practical. Everyone who touches the store works from the same rules, new staff have something to read on day one, and when a payment processor or anyone else asks how you operate, you can show the rules you actually follow. This guide sets out the sections to include, with sample wording you can adapt.

Why write it down

Government guidance on compliance programs is written mostly for larger organizations and specific areas of law, but its basic questions apply to a small store too. OFAC's framework for sanctions compliance expects written policies and procedures that reflect day-to-day operations, are easy to follow and are communicated to the staff who need them. The Justice Department's guide to evaluating corporate compliance programs asks whether policies are accessible to the employees they apply to, and whether there is a process for updating them as the business and its risks change.

Neither document is a template for a small supplier, and following them does not make a business compliant. They are useful as a checklist of what a reader will look for: rules that exist, that people know about and that match what actually happens.

Before you write

  • Walk through a real order from first visit to delivery and note every check and decision along the way.
  • Gather what you already have: terms of sale, shipping and refund policies, the checkout statement and any internal notes.
  • Name an owner for the policy. In a small business this is usually the owner of the company.
  • Keep the language plain. Short sentences and named roles are easier to follow than legal-sounding text.

The sections to include

1. Purpose and scope

Say what the policy covers and who it applies to. Sample wording: "This policy sets out how we sell research-use-only products to qualified business and research buyers. It applies to everyone who writes product copy, answers buyer questions, reviews orders or ships orders, including contractors."

2. Who you sell to

Describe your buyers and who you do not sell to. Sample wording: "We sell only to businesses, institutions and qualified researchers buying for laboratory research. We do not sell to consumers or to anyone buying for personal use." Add the destinations you do not ship to, or point to the document that lists them. How to verify business and research buyers covers what to check.

3. What you say and do not say

This section covers product pages, emails, social posts, support replies and packaging. State what product copy should contain: identity, specifications, testing documentation, storage and handling for the laboratory, and the research-use-only statement. Then state what it must never contain:

  • information about use in people or animals, of any kind
  • health, wellness, fitness, weight-loss, cosmetic or performance claims, stated or implied
  • testimonials, reviews or images that suggest either of the above

The FTC's small business advertising guidance says claims must be truthful and backed by evidence before they run, and that this applies to implied claims as well as express ones. Name who approves new copy before it goes live. Claims to remove from a research supply store is a useful companion to this section.

4. How orders are checked

List the checks every order goes through, in order. For example: the site-entry declaration, buyer type and credential checks, the signed research-use statement at checkout, destination checks and any hold rules. Say what happens when a check fails, and what kinds of order are held for a person to review. Authorize now, capture later explains how holds work.

5. Who decides

Name the roles, not just the people. Who can approve a held order, who can change copy, who can change the checks themselves, and who makes the final call on a hard case. A simple rule helps: the person who handled the sale does not approve their own held order. Compliance roles for small teams covers separation of duties at small scale.

6. How records are kept

Say what you record, where it is stored, who can access it and how long you keep it. Include buyer checks, signed statements, hold decisions, payments, copy changes and training. Data retention for compliance records covers retention periods and storage.

7. Problems and changes

Say how anyone on the team reports a problem, such as a claim found on a page or an order that shipped when it should have been held, and how it is logged, fixed and closed. OFAC's framework treats the ability of staff to report concerns without fear of reprisal as part of a culture of compliance. Write that commitment into your policy.

8. Training

Say who is briefed on the policy, when (before they get access to the store) and how often refreshers happen, and that each briefing is recorded.

9. Review

Set a review date, and list the events that trigger an earlier review: a new product line, a new market, a change in your checkout, feedback from your payment processor or a significant incident. The Justice Department's guide asks whether a program is reviewed so that it does not go stale, and whether it is updated with lessons from the company's own problems.

10. Approval and version

End with a version number, the date it took effect and the name of the person who approved it. Keep earlier versions so you can show which rules applied on a given date.

Make the policy match the store

  • Write what you do, not what sounds good. Anyone who compares your policy with your store and your order records will notice gaps.
  • Do not copy another business's policy. Its checks, roles and buyers will not match yours.
  • Keep it where people work. A policy nobody can find does not guide anyone.
  • Update it when practice changes. If you change a check, change the policy in the same week.
  • Ask a lawyer to review it. A qualified lawyer can review your policy and your terms of sale for your specific business.

What a written policy cannot do

A policy describes your controls. It does not make your store compliant, and it does not decide how a payment processor or card network will view your business. They make their own decisions. What a good policy does is make your controls consistent and visible.

If you use Claddr, several sections of the policy have a working counterpart. Your compliance profile, gate settings and statement versions are recorded, and an audit export for a date range includes a PDF summary of those controls as they were in force. How Claddr's audit record works explains what that record contains.

Sources

  1. 01OFAC: A Framework for OFAC Compliance Commitmentsofac.treasury.gov/media/16331/download?inline
  2. 02U.S. Department of Justice, Criminal Division: Evaluation of Corporate Compliance Programs (updated September 2024)www.justice.gov/criminal/criminal-fraud/page/file/937501/dl?inline
  3. 03FTC: Advertising FAQ's: A Guide for Small Businesswww.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business