A retail security RFP is your best chance to filter out providers who can’t actually protect your stores — before they’re standing in them. Most templates ask for a price and a headcount and stop there, which is exactly how retailers end up with a vendor that looked cheap and performed poorly. A well-built RFP interrogates whether a provider can operate in a retail environment: lawful apprehension, de-escalation, shrink data, coverage reliability, and technology. This step-by-step guide walks through how to scope, question, and evaluate so you buy performance, not the lowest number. For the standard to hold providers to, see our retail security and loss prevention services.

Step 1: Define your scope and risk first

Before you write a single question, define what you’re actually buying. Which stores, which hours, which posts, and what’s the risk at each? A flagship in a high-theft corridor needs a different scope than a quiet suburban location.

Ground this in data — your shrink baseline and incident history — so the RFP reflects real risk, not a guess. This is where a clear loss prevention program pays off: it tells you exactly what coverage each store needs, which makes every bid comparable against the same defined scope.

Skipping this step is the most common RFP mistake. Retailers who go to market with a vague “we need security for our stores” get back a scatter of bids that can’t be compared, priced against assumptions the providers invented. A precise scope — posts, hours, risk level, and expected outcomes per location — forces every bidder to answer the same question, and turns evaluation from guesswork into a genuine comparison.

Step 2: Ask the questions that separate real providers from pretenders

Weak RFPs ask about price. Strong ones demand evidence on what actually matters in retail:

  • Licensing and compliance. Is every officer PSISA-licensed, and how is it verified continuously?
  • Retail experience. What comparable retail clients and incidents can they point to? General guarding doesn’t transfer.
  • Training. What de-escalation and lawful-apprehension training do officers complete, and how often is it refreshed?
  • Staffing and fill rates. What are their real turnover and shift-fill numbers, and how do they cover a callout?
  • Reporting and data. How do they report incidents and shrink, and will you get the data?
  • KPIs and SLAs. What service levels will they commit to in writing, with consequences for misses?
  • Technology. How do they integrate with your cameras, EAS, and POS?
  • Insurance and liability. What coverage do they carry, especially around apprehension?

The rule: demand evidence, not adjectives. A capable provider answers with numbers and references; a weak one answers with reassurance.

Building or reviewing your RFP now? Book a consultation and we’ll help you pressure-test it.

Step 3: Set evaluation criteria before the bids arrive

Decide how you’ll score responses before you read them, so a slick proposal doesn’t sway you. Weight the criteria toward what protects your business — reliability, training, licensing, reporting, and references — rather than price alone.

In retail, quality should carry real weight, because the cost of a poor provider (rising shrink, wrongful-apprehension liability, staff turnover) dwarfs a small difference in rate. Build a simple scorecard, involve the right people (LP, operations, and procurement), and apply it consistently to every bid.

Deciding the weighting in advance is what protects you from your own instincts. A polished proposal and a confident pitch team are designed to impress; a scorecard set before the bids arrive keeps the focus on evidence — fill rates, references, training, licensing — rather than presentation. If a bid wins on your scorecard but your gut resists it, that’s worth examining honestly rather than quietly overriding the criteria you set for good reasons.

Step 4: Verify before you decide

The proposal is a sales document; verification is the truth. Before choosing:

  • Call references — comparable retailers, and ask specifically about reliability and how the provider handled problems.
  • Meet the people who’ll actually run your account, not just the pitch team.
  • Check the claims — licensing, insurance, and the training they described.
  • Pressure-test the transition plan, because a botched handover creates the very coverage gaps you’re trying to avoid.

A quick reference-call tip: ask what went wrong during the relationship and how the provider handled it, not just whether the client is happy. Every provider has had a bad shift or a difficult incident; the ones worth hiring are candid about it and can describe how they fixed it. A reference who insists everything was flawless is either unusually lucky or not being fully frank.

Then make sure everything you agreed lands in the contract — the clauses that matter are covered in reading a retail security service agreement. The weaknesses a sharp RFP surfaces are the same signs of an underperforming vendor you never want to discover after signing.

Frequently Asked Questions

Q1. What should a retail security RFP include?
Ans. A defined scope grounded in your risk, evidence-based questions on licensing, training, staffing, reporting, KPIs, technology, and insurance, clear evaluation criteria, and a verification step. Price is one factor, not the headline.

Q2. How long should the RFP process take?
Ans. Long enough for a thorough evaluation, reference checks, and a proper transition. Rushing it is how retailers end up switching again within a year.

Q3. Who should be involved in evaluating bids?
Ans. Loss prevention, store operations, and procurement at minimum. The people who work alongside security day to day surface issues a pure procurement lens misses.

Q4. Should I weight price or quality more heavily?
Ans. In retail, quality should carry significant weight, because a poor provider’s costs — rising shrink, liability, turnover — far exceed a small difference in rate.

Q5. What’s the most overlooked question in security RFPs?
Ans. Shift-fill and turnover rates. Retailers focus on the pitch and forget to ask who will actually stand the posts, and how reliably.

Q6. How do I compare bids that include different things?
Ans. Standardize the scope so every bid answers the same requirements, then compare what drives each price rather than the headline number alone.

Q7. Should I check references and do site visits?
Ans. Yes. Speaking to comparable retailers and meeting the people who’ll run your account tells you far more than any written proposal.

Q8. Why does apprehension training belong in an RFP?
Ans. Because wrongful arrest or excessive force in a store creates serious liability. You want evidence that officers are trained on the lawful limits of apprehension.

Q9. Should the incumbent provider be invited to bid?
Ans. Often yes, if performance has been acceptable, so you can benchmark them objectively — while holding them to the same standard as everyone else.

Q10. What happens after we choose a provider?
Ans. A structured transition and onboarding, then ongoing performance reviews against the KPIs you agreed. The RFP sets the standard; the contract and reviews enforce it.

A retail security RFP done right filters out providers who can’t operate in a store before they’re hired. Scope from real risk, demand evidence over adjectives, score against what protects your business, and verify before you sign — and you’ll choose a partner instead of a price.

Ready to build an RFP that protects your stores? Request a consultation with our retail team.