FSVP compliance · Very small importer guide

The Very Small Importer Who Thought FSVP Would Be Simple

A practical guide for very small importers to understand applicable FSVP responsibilities, organize records, manage suppliers, and create a process that fits the size of the business.

In this article

The business was small.

There were only a few employees, one foreign supplier, and a limited number of imported products.

The owner personally handled most of the important decisions, from purchasing and supplier communication to shipment coordination, inventory, and customer questions.

When FSVP first came up, the reaction was simple:

“We only import a small amount. How complicated can this be?”

It sounded reasonable.

The business wasn't importing hundreds of products.

There wasn't a large supplier network.

There wasn't a regulatory department.

FSVP seemed like one more piece of paperwork that could be handled when the shipment was being prepared.

Then the owner started asking questions.

Who evaluates the supplier?

What information should the supplier provide?

What verification is needed?

Where should the records be kept?

What happens when something changes?

And perhaps the most important question:

“What exactly am I responsible for?”

That's when the importer discovered something many very small businesses eventually learn:

FSVP may be manageable, but it shouldn't be treated casually.

The challenge isn't necessarily the size of the business.

The challenge is understanding what applies, assigning responsibility, maintaining the applicable records, and creating a process that works even when one person is handling almost everything.

---

Small Does Not Automatically Mean Simple

One of the easiest assumptions for a very small importer to make is that the size of the business determines the amount of compliance required.

It doesn't work quite that way.

The FSVP regulation provides modified requirements for certain qualifying very small importers and very small foreign suppliers under 21 CFR §1.512. However, whether those modified requirements apply depends on the applicable criteria and circumstances.

So the first question isn't:

“We're small. Do we really need FSVP?”

The better question is:

“What requirements apply to our specific importing situation?”

That distinction is important.

A small business can still have meaningful responsibilities when it imports food into the United States.

At the same time, being small can make the process more manageable.

A company with one supplier and a few products doesn't need to build the same infrastructure as a company managing hundreds of suppliers.

It needs a process appropriate to its actual operation.

That means the goal should not be to make compliance unnecessarily complicated.

The goal is to understand the applicable requirements and create a practical way to manage them.

---

The Importer Who Thought the Documents Would Be Enough

The owner contacted the supplier and started collecting paperwork.

A certificate arrived.

Then a product specification.

Then an audit document.

Then testing information.

Everything was saved.

The owner felt relieved.

“Okay. We have the documents.”

But another question soon appeared:

“What do these documents actually tell us about the supplier and the food?”

That question changed the way the importer looked at FSVP.

The objective wasn't simply to collect documents.

The information needed to support the applicable evaluation and verification process.

A certificate might be useful.

An audit report might be useful.

Testing information might be useful.

A product specification might be useful.

But each document needs to be understood in context.

The importer needs to know what the information demonstrates and how it fits into the overall FSVP.

That's an important distinction for any importer, but especially for a very small business where one person may be responsible for the entire process.

A folder full of documents can create the appearance of compliance.

A functioning FSVP should provide something more useful:

A clear record of what was considered, what was determined, what verification was performed, and what needs to happen when circumstances change.

---

Then the Supplier Said, “We've Always Done It This Way.”

The importer had worked with the supplier for years.

There was trust.

The supplier was responsive.

Products had arrived without major issues.

So when the owner learned that supplier evaluation and verification were part of FSVP, the reaction was:

“Why do I need to keep reviewing a supplier I already know?”

Because familiarity and verification are different things.

A good supplier relationship is valuable.

It can make communication easier.

It can make document collection faster.

It can make resolving questions less difficult.

But an importer still needs to understand the applicable FSVP requirements and maintain the appropriate records.

A supplier can also change.

The facility can change.

The manufacturing process can change.

The product can change.

New information can become available.

The fact that everything was fine last year doesn't automatically mean the same information remains sufficient forever.

A strong relationship should make the compliance process easier.

It should not replace the process.

---

The Day the Product Changed

Eventually, something did change.

The supplier introduced a change to the product.

It might have been a formulation change.

It might have been a manufacturing change.

It might have involved a different production facility.

The product still had the same name.

The supplier was still the same company.

At first, the importer didn't think much of it.

But this time, the owner had learned an important lesson:

A supplier relationship needs ongoing attention.

When significant new information or changes could affect the adequacy of an FSVP, the importer may need to reevaluate the program as applicable.

This is one reason FSVP shouldn't be treated as a one-time project that disappears after the first shipment.

The program needs to remain connected to the actual business.

The supplier that was evaluated when the relationship began may not be exactly the same supplier years later.

The food that was originally reviewed may not be produced under exactly the same circumstances.

And the records that were appropriate at one point may eventually need to be updated.

The objective is not to create unnecessary work every time something changes.

It is to recognize when a change is significant enough to require attention.

---

The Real Problem Wasn't That FSVP Was Too Complicated

After working through the process, the importer realized something.

FSVP itself wasn't necessarily the problem.

The problem was that there had been no system.

Supplier information was spread across email.

Documents were saved in different folders.

Important decisions were remembered rather than documented.

Nobody had a clear schedule for reviewing the supplier.

Nobody had clearly defined what should happen when information changed.

The importer had been managing compliance reactively.

That is a common challenge for very small businesses.

When only one person is responsible for everything, compliance can become dependent on memory.

And memory works well—until the business gets busy.

The owner may know exactly why a supplier was selected.

They may remember a conversation with the supplier's quality manager.

They may know where a particular document was saved.

But if the information isn't organized, another person may not be able to understand the program.

That creates unnecessary dependency on one individual.

A practical compliance process should reduce that dependency.

---

When “I'll Do It Later” Becomes the Problem

The owner kept intending to organize everything.

After the next shipment.

After the next customer order.

After the next busy season.

But every new priority pushed FSVP further down the list.

This is how small businesses can unintentionally create compliance gaps.

Not because they don't care.

Not because they are deliberately avoiding their responsibilities.

Simply because there is always something that feels more urgent.

The problem is that FSVP often becomes urgent at exactly the wrong time—when a shipment is already moving or someone is asking for documentation.

By then, the importer has fewer options and less time.

The supplier may be busy.

The requested information may take time to obtain.

The importer may have to search through old emails.

And the owner may suddenly be trying to solve a compliance problem while simultaneously managing the rest of the business.

That is rarely the best time to build a system.

---

FSVP Should Be Part of the Import Process

A better approach is to build FSVP into the normal import workflow.

When a supplier is being considered, the importer begins gathering the appropriate information.

When a product is selected, the importer understands what information is relevant.

Before a shipment is prepared, the importer knows where the applicable FSVP records are.

When the supplier changes something, there is a process for determining whether the change affects the program.

That means the importer isn't starting from zero every time a shipment arrives.

Instead, compliance becomes part of the normal business process.

A simple workflow can help:

Supplier selected → Product reviewed → Applicable FSVP activities identified → Records organized → Verification addressed → Shipment prepared

Instead of:

Shipment moving → Someone asks about FSVP → Documents searched for → Supplier contacted → Compliance process starts

The difference is planning.

The first approach makes FSVP part of the business.

The second makes FSVP an emergency.

---

What Does a Very Small Importer Actually Need to Manage?

The exact requirements depend on the circumstances, but a very small importer should have a clear understanding of several basic areas.

The supplier

Know who is actually manufacturing or supplying the food.

The importer should have sufficient information to identify the foreign supplier and support the applicable evaluation and verification process.

The product

Know what food is being imported and maintain the relevant product information.

The importer should understand what food is covered by the applicable FSVP activities.

The evaluation

Understand how the supplier and applicable food safety information are being considered.

The evaluation should be appropriate to the food, supplier, and circumstances.

Verification

Understand what applicable verification activities are required and how they are documented.

Verification should not simply be selected because it is convenient or because a generic checklist says to perform it.

Records

Keep the relevant information organized and accessible.

The importer should be able to locate the records supporting the applicable FSVP activities.

Changes

Have a process for recognizing significant changes and determining whether further action is appropriate.

A supplier change, product change, or other new information should not automatically disappear into an email inbox.

Responsibility

Someone needs to clearly own the FSVP process.

That person does not necessarily need to be a full-time compliance employee.

But the responsibility should be clear.

These concepts may sound straightforward.

The difficulty is making them work consistently.

---

A Small Business Doesn't Need a Huge Compliance Department

This is where very small importers sometimes become discouraged.

They see large companies with extensive supplier management programs and think:

“We could never do all of that.”

You probably shouldn't try to.

A large company may need complex workflows because it has hundreds of suppliers, multiple facilities, many products, and dedicated compliance personnel.

A very small importer may need a much simpler structure.

The goal is not to imitate a large company.

The goal is to create a process that is:

Appropriate

Organized

Maintainable

Understandable

That's what makes a compliance system useful.

A small importer should not create paperwork simply because larger companies have paperwork.

At the same time, the importer shouldn't assume that simplicity means no documentation is needed.

The right system is the one that provides enough structure to manage the applicable responsibilities without overwhelming the business.

---

When an FSVP Toolkit Can Help

Some very small importers want to remain directly involved.

They have the time.

They want control.

They have someone internally who can manage the records.

For those businesses, an FSVP Toolkit can provide a practical starting point.

Instead of trying to determine what documents to create and how to organize everything from scratch, the importer has a structured framework to work from.

The toolkit can help the importer organize the information needed for the FSVP process and provide a repeatable structure for managing the records.

This can be particularly useful for a very small importer with a limited supplier and product base.

The toolkit doesn't remove the need for the importer to understand and manage its responsibilities.

It simply makes the process more organized.

The importer still needs to apply the framework to the actual food, supplier, and circumstances.

The objective is to give a small business a practical way to manage its program rather than forcing it to build everything from a blank page.

---

When Implementation Support Makes More Sense

Other importers reach a different conclusion.

They may say:

“I don't know how to turn the regulation into an actual program.”

That's different from simply needing templates.

Implementation support can help the importer understand how the pieces fit together.

The focus becomes:

What applies to this business?

What needs to be documented?

How should the supplier information be evaluated?

What verification activities are relevant?

How should the records be organized?

How should the program be maintained?

This can be particularly useful for a first-time importer who wants to establish the process correctly from the beginning.

The goal isn't simply to produce a completed set of documents.

It is to establish a program that the importer can actually understand and maintain.

That distinction matters.

A small importer should not end up with a set of documents that nobody knows how to use.

---

When a Gap Assessment Can Provide Clarity

Some very small importers already have an FSVP.

Their concern is different:

“We created this ourselves. Is it actually enough?”

That is where a readiness or gap assessment can be valuable.

Instead of guessing, the importer can have the existing program reviewed for potential weaknesses.

The review may identify areas such as:

• Missing information
• Incomplete records
• Outdated documents
• Unclear responsibilities
• Supplier changes
• Product changes
• Process weaknesses
• Records that are difficult to locate

Sometimes the review confirms that the importer is on the right track.

That confirmation can be just as valuable as finding a problem.

If gaps are identified, the importer can then focus resources on the areas that actually need attention rather than rebuilding everything unnecessarily.

That is one reason an assessment can be useful.

The goal is not automatically to replace the entire program.

The goal is to understand what is actually there.

---

When Ongoing Support Becomes the Better Choice

A business may begin with one supplier.

Then it adds another.

Then another product.

Then shipments become more frequent.

Suddenly, the owner is spending hours every month requesting documents, reviewing information, tracking changes, and maintaining records.

At that point, the business may realize:

“FSVP has become another job.”

That is when ongoing support can become practical.

The goal isn't to remove the importer from the process.

It is to help manage recurring compliance activities so the business owner can focus on running the business.

Ongoing support may be particularly useful when there is no internal employee with sufficient time or technical knowledge to manage recurring FSVP activities.

The business may still make the important decisions.

Professional support can help keep the process organized, maintain records, follow up on documentation, and identify issues that require attention.

---

Don't Forget the Cost of Doing It Yourself

Professional services have a cost.

But internal compliance work has a cost too.

Consider the time spent:

• Sending supplier follow-ups
• Reviewing certificates
• Organizing records
• Tracking changes
• Researching requirements
• Preparing documentation
• Resolving questions
• Updating the FSVP
• Determining what needs to happen next

For a very small company, that time often comes directly from the owner.

The real question isn't simply:

“Can I do this myself?”

It is:

“Is this the best use of my time?”

Sometimes the answer is yes.

Sometimes it isn't.

If the owner has the knowledge, time, and structure to manage the program, internal management may make sense.

If the owner is spending hours trying to determine what documents are needed or what should happen next, professional support may provide considerably more value.

The objective is not to outsource everything.

It is to use the right level of resources for the business.

---

A Practical Check for the Very Small Importer

Before your next shipment, ask:

Can I identify my foreign supplier?

Can I identify the food being imported?

Can I locate the current FSVP records?

Can I explain how the supplier was evaluated?

Can I identify the applicable verification activities?

Do I know what happens if the supplier changes something?

Is someone clearly responsible for maintaining the program?

Could someone else understand the program if the person normally handling it were unavailable?

If you cannot answer several of these questions, don't immediately assume that your business is in trouble.

Instead, treat the uncertainty as a reason to review the program.

Finding the weakness early is much easier than discovering it when a shipment is already moving.

A review may reveal that most of the necessary information already exists.

Or it may show that several important pieces are missing.

Either way, the importer now has something valuable:

Clarity.

---

The Lesson for Very Small Importers

The importer who thought FSVP would be simple eventually learned that the problem wasn't the size of the business.

The problem was assuming that small meant informal.

A small importer can have a focused FSVP.

It can have fewer suppliers.

It can have fewer products.

It can have a simpler workflow.

It can have fewer people involved.

But it still needs a process that reflects its actual responsibilities.

The goal isn't to make compliance bigger than the business.

The goal is to make compliance fit the business.

That means understanding what applies.

Knowing who is responsible.

Organizing the relevant information.

Addressing the applicable verification activities.

Maintaining the records.

And recognizing when something changes.

For a very small importer, that can be enough to turn FSVP from something that feels overwhelming into something that is simply part of the normal importing process.

---

Don't Let “We're Too Small” Become the Reason You Wait

Very small businesses often have an advantage that larger organizations don't.

The decision-making process can be fast.

The owner may have a direct relationship with the supplier.

There may be only a few products to manage.

The importer may be able to make changes quickly.

Use those advantages.

Don't let the size of the business become a reason to postpone the process.

You don't need to build a multinational compliance department.

You don't need to create hundreds of forms.

You don't need to make FSVP more complicated than the business requires.

But you do need to understand what applies and establish a process you can actually maintain.

Because the smaller the organization, the more important it can be to make sure the process doesn't depend entirely on one person's memory.

---