The FSVP Gaps Importers Usually Don't See Themselves

Most importers are not ignoring their FSVP.

They are usually doing the opposite.

They collect supplier documents.

They request certifications.

They communicate with foreign suppliers.

They maintain records.

They review shipments.

They answer customer questions.

They may even have an FSVP program that has been in place for years.

So why do gaps still happen?

Because some of the most important FSVP weaknesses are difficult to see from inside the organization.

The importer sees the work being done.

An outside reviewer sees what the system actually demonstrates.

That difference matters.

The importer who was sure everything was covered

Imagine an importer preparing for an internal compliance review.

The team isn't worried.

They have a supplier folder for every major supplier.

They have certificates.

They have audits.

They have product specifications.

They have FSVP documents.

Someone says:

“I think we're in pretty good shape.”

And they probably are.

But the review reveals several issues.

Nothing looks catastrophic.

There isn't one giant failure.

Instead, there are small disconnects.

A supplier was added but not formally incorporated.

A product changed.

A certificate is outdated.

A verification record doesn't clearly explain the conclusion.

A facility changed.

An annual review wasn't documented.

Each issue seems small.

Together, they tell a different story.

Why importers don't always see their own gaps

There are several reasons.

You know the history

Your team remembers what happened.

You know the supplier

You've worked with them for years.

You know where the documents are

Even if they're not organized perfectly.

You know why a decision was made

Even if the reasoning isn't clearly recorded.

You see the work happening

Even when the process isn't formally documented.

This creates a natural blind spot.

You see the context.

A reviewer sees the evidence.

Gap #1: Assuming the FSVP covers everything

This is one of the easiest gaps to miss.

The importer has an FSVP and assumes:

“Our imports are covered.”

But the business may have changed since the FSVP was created.

New:

• Suppliers
• Products
• Facilities
• Formulations
• Manufacturing arrangements
• Import channels

The FSVP may not have been updated at the same pace.

The solution starts with a simple comparison:

What are we importing today versus what does our FSVP actually cover?

Gap #2: Treating the supplier as the unit of compliance

Importers sometimes think:

“Supplier ABC is approved.”

Therefore:

“Everything we buy from Supplier ABC is covered.”

That can be too simplistic.

Different foods can involve different hazards, processes, facilities, and verification considerations.

A supplier relationship doesn't automatically answer every product-level question.

The review needs to connect:

Supplier

to

Food

to

Hazards

to

Evaluation

to

Verification

Gap #3: Confusing a certification with supplier verification

A supplier may have:

SQF certification

BRCGS certification

FSSC 22000 certification

Organic certification

HACCP documentation

These may provide valuable information.

But the importer still needs to understand how the evidence fits into its FSVP evaluation and verification process.

The common assumption is:

“They're certified, so we're covered.”

The better question is:

“What does this certification establish, and how does it support our FSVP decision?”

Gap #4: Having an audit but not clearly documenting what it means

An audit report can be valuable evidence.

But simply placing it inside a supplier folder doesn't explain:

Why the audit was selected

What it covered

Who performed it

What findings were identified

How findings were handled

What conclusion the importer reached

The importer may understand all of that.

The file may not.

That's the gap.

Gap #5: Using old information because it was once valid

This is extremely common.

The importer finds a document and thinks:

“We have it.”

But the real question is:

“Is it still current and relevant?”

A supplier certificate from several years ago may no longer represent the current status.

An old audit may not address a changed facility.

An old questionnaire may not reflect current operations.

The document isn't necessarily wrong.

It may simply be old.

Gap #6: Not noticing supplier changes

A supplier might change:

• Manufacturing facility
• Ownership
• Production process
• Ingredients
• Quality personnel
• Certification
• Contract manufacturer

The supplier may still have exactly the same name.

That makes changes easy to overlook.

The importer may continue treating the supplier as unchanged because the purchase order looks the same.

Gap #7: Assuming “same supplier” means “same risk”

This is another subtle issue.

A long-term supplier relationship creates familiarity.

Familiarity can become assumption.

The importer thinks:

“We've used them for years.”

But the relevant question is:

“What is true about the supplier and food today?”

Experience is useful.

It should not replace verification.

Gap #8: Forgetting that products change

A product may appear unchanged from the outside.

Same:

Brand

Product name

SKU

Packaging

But the formulation may change.

An ingredient may change.

A processing step may change.

A manufacturing facility may change.

A supplier may change.

Those changes can create new compliance questions.

Gap #9: New products bypassing the FSVP process

This often happens during business growth.

Marketing launches a product.

Purchasing finds a supplier.

Operations schedules production.

Logistics arranges the shipment.

Everyone is doing their job.

But nobody tells the FSVP owner.

The product arrives in the business before the compliance file is updated.

The problem isn't lack of effort.

It's a missing workflow connection.

Gap #10: New suppliers being approved commercially but not through the FSVP process

The purchasing team may evaluate:

Price

Quality

Lead time

Capacity

Payment terms

Then the supplier is approved.

But where does FSVP fit?

If FSVP review happens after commercial approval—or worse, after the first shipment—the compliance process is reactive.

A stronger workflow incorporates FSVP requirements into supplier onboarding.

Gap #11: Relying on one employee's memory

This is one of the most dangerous hidden weaknesses.

Ask:

“Why did we choose this supplier verification activity?”

The compliance manager knows.

Ask:

“Why was this supplier approved?”

The compliance manager knows.

Ask:

“Why wasn't additional verification performed?”

The compliance manager knows.

Then ask:

“Where is that documented?”

The answer may be:

“It isn't.”

Now the organization has discovered a knowledge-management gap.

Compliance shouldn't live inside someone's head

People leave.

Roles change.

Companies grow.

A strong FSVP should preserve important decisions in records.

The next employee should not need to interview the previous employee to reconstruct the program.

Gap #12: Assuming a document exists because someone said it was sent

This is surprisingly common.

Supplier:

“We sent the certificate.”

Importer:

“Okay.”

But where is it?

Maybe it's in:

Email

Spam

A shared folder

An employee's inbox

A supplier portal

If nobody can quickly locate the document, the importer has an operational problem even if the document technically exists.

Gap #13: Document control that depends on filenames

Consider a folder containing:

Audit.pdf

Audit-new.pdf

Audit-final.pdf

Audit-final2.pdf

Audit-Updated.pdf

Which one is current?

The employee may know.

The system doesn't.

Good document control should make current status obvious.

Gap #14: Not connecting corrective actions to supplier evaluation

A supplier audit identifies a significant finding.

The supplier provides corrective action.

The importer files the response.

Then everyone moves on.

But did the importer consider what the finding means for the supplier relationship?

That is the question.

Corrective action should not necessarily be treated as an isolated document.

It can provide information relevant to supplier evaluation and verification decisions.

Gap #15: Assuming no complaints means no supplier concerns

An importer may think:

“We've never had a customer complaint.”

That's positive.

But customer complaints are only one source of information.

Supplier compliance can involve many other sources:

Audit findings

Regulatory information

Certification status

Supplier changes

Food safety events

Testing

Verification activities

The absence of complaints doesn't automatically prove that the supplier file is current.

Gap #16: Not documenting what happens after a change

Suppose the importer learns:

“The supplier has opened a new production facility.”

The team investigates.

They determine that the existing approach remains appropriate.

That's potentially a perfectly reasonable outcome.

But where is that conclusion?

If there is no record, a future reviewer may see:

Old facility information

and

New facility information

without understanding what happened in between.

Documentation connects the dots.

Gap #17: Treating annual review as a calendar event instead of a management process

An annual review shouldn't simply mean:

“Open the supplier folder once a year.”

It should answer:

What changed?

What remains current?

What evidence needs updating?

What issues remain open?

What needs reevaluation?

What should happen next?

The date matters.

The analysis matters more.

Gap #18: Not knowing which suppliers are overdue

Ask your team:

“Which supplier assessments are overdue?”

If someone has to manually search through multiple spreadsheets, that's a weakness in the management system.

The problem isn't necessarily regulatory.

It's operational.

But operational weaknesses can eventually create compliance weaknesses.

Gap #19: The FSVP isn't connected to shipment activity

This is one of the most revealing tests.

Select a recent import.

Can you quickly identify:

Importer

Foreign supplier

Food

Facility

Applicable FSVP records

Verification information

Current supplier status

If the answer is no, there may be a disconnect between compliance management and actual importing activity.

Gap #20: The importer is focused on documents instead of decisions

This is perhaps the biggest hidden gap of all.

A compliance file isn't strong simply because it contains many documents.

The real question is:

“What decisions did the importer make, and what evidence supports those decisions?”

Documents are inputs.

FSVP management requires decisions.

The gap most importers don't expect

Sometimes the biggest discovery is:

“We're doing the work, but we're not documenting it consistently.”

That can actually be good news.

The organization may already have the right knowledge and processes.

It needs to make them visible and repeatable.

Another unexpected discovery: the process is too complicated

A gap assessment can also reveal the opposite problem.

The importer may have:

Multiple spreadsheets

Duplicate questionnaires

Three document repositories

Several approval forms

Manual reminders

Separate supplier databases

The team is spending enormous amounts of time maintaining compliance.

The program isn't necessarily weak.

The system is inefficient.

That is an important distinction.

A gap assessment should identify both risks and inefficiencies

A good review should ask:

Where could compliance fail?

but also:

Where are we creating unnecessary work?

Both matter.

The goal is a system that is:

Compliant

Documented

Practical

Maintainable

Scalable

The importer may be stronger than it thinks

This is worth remembering.

An assessment isn't a search for bad news.

You may discover:

• Strong supplier relationships
• Current certifications
• Good verification records
• Clear product information
• Effective supplier communication
• Well-maintained records

The assessment confirms those strengths.

Then you can focus resources on the areas that actually need improvement.

Why a fresh perspective helps

Someone outside the day-to-day operation is less likely to accept:

“That's how we've always done it.”

They ask:

“Why?”

They don't automatically accept:

“The supplier is approved.”

They ask:

“Based on what?”

They don't assume:

“This is the current document.”

They ask:

“How do you know?”

Those questions create visibility.

The goal isn't to embarrass the importer

This is important.

Compliance reviews can sometimes feel personal.

They shouldn't.

A gap is not a judgment of the employee who maintained the file.

It is information about the system.

The right response is:

“We found it. Now let's fix it.”

What happens when the gaps become visible?

The importer can prioritize.

Immediate

Address issues that may affect current imports or significant compliance responsibilities.

Short term

Update documentation and close process weaknesses.

Ongoing

Build monitoring and maintenance into normal operations.

That creates a practical improvement plan instead of a panic response.

You don't need to fix everything at once

One of the biggest mistakes after a gap assessment is trying to rebuild the entire FSVP immediately.

Don't.

Start with:

What matters most?

Then:

What is easiest to correct?

Then:

What requires deeper technical review?

Then:

What system change prevents recurrence?

That sequence keeps the project manageable.

The real purpose of a gap assessment

It's not:

“Find everything wrong.”

It's:

“Understand where the program stands so the importer can make informed decisions.”

That is a much more useful objective.

When should an importer consider a gap assessment?

It can be especially useful when:

• The FSVP hasn't been reviewed recently
• The importer has added suppliers
• The importer has added products
• The supplier base has grown
• A supplier changed facilities
• Compliance responsibilities changed hands
• The company is preparing for an FDA inspection
• Records are scattered
• The importer is unsure whether current imports are covered
• Management simply wants an independent assessment

You don't need a known violation to justify a readiness review.

The question isn't “Do we have gaps?”

Every evolving compliance system can have gaps.

The better questions are:

Which gaps do we have?

How important are they?

Why did they occur?

How do we correct them?

How do we prevent them from returning?

Those questions turn compliance into management.