How Do I Figure Out How Many Reps to Schedule at Each of My Multi-Unit Cell Phone Stores in 2026?

The outcome you should expect

The change you are buying with this method is not a smaller labor line — it is a labor line that moves with gross profit instead of moving with store hours. Most multi-unit wireless operators start from one of two default patterns, and both are expensive in different ways. The first default is flat staffing: every store gets the same crew, usually two on weekdays and three on weekends, because that is what the district manager decided two years ago and nobody revisited it. The second default is open-to-close coverage: each store is staffed to fill the hours the mall or strip center requires it to be open, which means a rep standing at the counter at 10:15 a.m. on a Tuesday because the lease says the gate must be up, not because anyone is walking in.

Both defaults produce the same two symptoms. Your highest-volume locations run short during the after-work window and you lose activations you already paid to attract — the customer walked in, waited eleven minutes, and left to think about it. Meanwhile your slowest locations carry a rep whose entire day produced one screen protector and a bill-pay. The dollars lost on the busy store are conversion dollars; the dollars lost on the slow store are wage dollars. The gross-profit division attacks both at once because it is a two-sided constraint, not a cost-cutting exercise.

Expect three concrete outcomes once you run the math honestly. First, your store-level headcount will stop being uniform. In a typical eight-to-twelve-store chain, you will find a spread where the strongest location needs five or six bodies on a Saturday and the weakest needs two — and you will find that you have been scheduling both of them at three-and-four. Second, your per-rep productivity number becomes a real management metric instead of a vague sense that "Marcus is good." When every rep is scheduled against a $250-a-day floor, a rep producing $140 a day is visibly under, and a rep producing $410 is visibly carrying weight you should be paying for. Third — and this is the outcome operators underestimate — accessory attach and activation rates usually improve at your overstaffed stores after you cut a body. Four reps splitting eleven ups means each rep gets under three real chances to sell, they get lazy about the pitch because another up is walking in, and nobody owns the outcome. Three reps splitting the same eleven ups work harder per customer.

What you should not expect is an immediate payroll drop across the board. In practice the math redistributes more than it cuts. Hours come off the slow Tuesday morning at three locations and go onto the Saturday afternoon at your two flagships. Total hours might move five to ten percent; gross profit per labor hour moves considerably more because those hours are now sitting where the activations ring. Treat labor dollars as a portfolio you are reallocating across stores, not a number you are shrinking.

What drives that outcome

Two inputs drive everything: the per-rep daily gross-profit target, and each store's trailing gross profit by day of week. Get those two right and the arithmetic is trivial. Get either wrong and you will schedule confidently to a wrong answer.

Start with the target, because it is the number people fight about. In wireless retail, gross profit per rep is not device margin alone — device margin on a flagship phone is thin and sometimes negative once you account for promotional credits. The real gross profit stack is four layers: hardware margin, accessory margin (which is where most of the dollars actually live, often at 50 percent or better), activation and upgrade spiffs from the carrier, and any protection-plan or service-plan attach commission. When you set a per-rep number, you have to name which of those four you are counting, and you have to count the same four in the store-level data you divide. Mixing definitions — target built on all four, store data pulled on hardware only — is the single most common way this method breaks.

Set the target as a floor for an average rep on an average day, not a stretch goal. Something in the neighborhood of $250 a day is a reasonable starting point for a typical authorized-retailer store, but the honest way to derive your own is backward from history: take twelve weeks of total gross profit for the chain, divide by total rep-days worked in that window, and you have your current actual. If that number comes out at $215, do not set the target at $400 because it sounds ambitious — you will schedule yourself into permanent understaffing and blow up your conversion. Set it at or slightly above the current actual, in the $230 to $270 range in that example, and raise it deliberately as coaching and product mix improve.

The second input is store-and-day gross profit, averaged over three to six months. Three months is the minimum that smooths a single bad week; six months is better if your chain has stable traffic. Do not average across days — Saturday and Tuesday are different businesses in the same building. Pull a grid: rows are stores, columns are the seven weekdays, cells are average gross profit. That grid is the whole input. Every headcount number falls out of dividing a cell by your target.

A third factor shapes placement rather than count: receipt timing. Headcount answers how many; the hourly receipt distribution answers when. Pull your transaction timestamps for the same three-to-six-month window and bucket them by hour. Nearly every phone store shows the same double hump — a lunch bump roughly 11:30 to 1:30, and a heavier after-work build from about 4:30 until an hour before close, with Saturday afternoons flattening into one long peak. Your calculated headcount for a given day should be layered against that curve: the opener carries the morning alone, the second rep comes in before lunch, and the third through fifth land in the early afternoon so they are on the floor when the surge hits. Scheduling all five reps at 10 a.m. because the number said five is a misread of the method.

Benchmarks and realistic ranges

Here is what the arithmetic looks like across a real spread of locations, so you can sanity-check your own grid against something concrete rather than deriving it in the abstract.

Take a target of $250 per rep per day and a five-store chain. A mall kiosk with heavy weekend foot traffic might average $1,250 gross profit on Saturday, $900 on Sunday, and $450 to $600 Monday through Thursday. The division gives you five on Saturday, four on Sunday (3.6, rounded up), and two on the weekdays (1.8 to 2.4). A strip-center store next to a grocery anchor might run $700 Saturday, $500 Tuesday, and $650 Friday — three, two, and three. A rural single-anchor store might sit at $375 every day of the week, which is 1.5 reps: one rep with a partial second shift covering the peak, not two full bodies.

Notice how the fractions behave. Fractional results are the useful part, not a rounding annoyance. A 3.6 means you need three full reps plus a six-hour partial, not four full ten-hour shifts. Convert fractions honestly by treating a rep-day as your standard shift length — if a full shift is eight hours, then 0.5 reps is a four-hour shift, and 3.6 reps is roughly three full shifts plus a five-hour overlap dropped onto the peak window. Rounding every fraction up is how operators quietly rebuild the overstaffing they were trying to fix; rounding every fraction down is how they lose the Saturday close.

On ranges for the target itself: the number varies enormously by channel and market. A high-volume corporate store in a dense metro with strong accessory discipline will support a materially higher per-rep target than a rural authorized retailer whose mix is heavy on prepaid and bill-pay. Rather than borrowing someone else's benchmark, derive yours and then track its drift. If your chain-wide actual GP per rep-day is climbing quarter over quarter while headcount holds flat, your coaching is working. If it is falling while headcount holds flat, either your mix deteriorated or you have quietly overstaffed — the metric does not tell you which, but it tells you to go look.

A second useful benchmark is gross profit per labor hour, which is the same idea at finer resolution and is the number to watch when you have split shifts and partial coverage. Compute it weekly per store. The stores that look fine on a daily basis but bad per labor hour are almost always the ones carrying dead morning coverage.

For the physical ceiling: no matter what the division says, a store cannot productively hold more reps than it has customer-facing positions plus one. A three-station store with six reps scheduled is a store where three reps are standing behind the others. Cap headcount at roughly one rep per station plus one floater, and if the math consistently demands more than that cap, you do not have a scheduling problem — you have a capacity problem, and the answer is extended hours, a second register, or a relocation, not more bodies on the same floor.

Finally, on rate of change: recompute store schedules monthly against a rolling three-month average, and revisit the per-rep target quarterly. Monthly is frequent enough to catch a new competitor opening across the parking lot or a seasonal shift, and slow enough that your reps are not getting a structurally different schedule every week. Rep retention in wireless retail is fragile; schedule volatility is one of the cheapest ways to lose a good closer.

Risks, edge cases, and failure modes

The most dangerous failure mode is running this method on a store whose gross profit is depressed *because* it is understaffed. The division then confirms the understaffing and you cut further, traffic converts worse, next month's average drops again, and you have engineered a death spiral into a location that was actually fine. Guard against it by checking conversion rate and walkout indicators alongside gross profit before you cut any store. If a store's traffic count is healthy and its close rate is poor, the problem is coverage or coaching, not demand — do not let the formula cut it.

The mirror-image failure is a store propped up by a temporary promotion. A carrier runs an aggressive trade-in offer, one location happens to sit near a competitor's closing store, and its three-month average inflates. You staff to the inflated number, the promotion ends, and you are carrying two extra bodies. This is why the rolling window matters and why you should look at the trend line, not just the average. A store whose gross profit is 40 percent above its own six-month baseline for a single month is a store to watch, not a store to permanently staff up.

Watch for the minimum-coverage collision. Most operators have a policy — sometimes an insurance or loss-prevention requirement — that a store is never staffed with one person, or is never opened or closed alone. When the division returns 1.2 reps for a slow location and your policy requires two-deep, the policy wins and you accept that the store runs below target on that day. Do not pretend the math said two. Log it as a policy override, because the accumulation of those overrides is a real number and it may eventually tell you that a location cannot support its own coverage floor and should be consolidated or moved to reduced hours.

Part-time and split shifts create arithmetic errors when people convert carelessly. A rep working four hours against an eight-hour standard is 0.5 rep-days, and their contribution to the target is $125, not $250. If your chain runs heavily part-time, do the whole calculation in rep-hours rather than rep-days — divide the daily gross profit by a per-rep-hour target — and the fractions stop biting.

Multi-function stores need separate pools. If a location runs a repair bench alongside the sales floor, repair gross profit and sales gross profit are different businesses with different per-head economics, and blending them will overstate how many *sales* reps you need. Compute each pool against its own target and sum the headcount, but be careful not to double-count a technician who also takes ups during a rush.

Two softer risks are worth naming because they kill adoption rather than accuracy. The first is presenting this to store managers as a labor-cut initiative. It will be received as one, they will game the gross-profit reporting, and your inputs will rot. Present it as what it is — the store that earns coverage gets coverage — and pair the rollout with a visible reallocation of hours *toward* your busiest stores so managers see the method giving as well as taking. The second is the target becoming a stick. If $250 a day is framed as a quota with consequences, reps will chase the easiest gross profit available and your mix will distort. Frame it as the floor that justifies the shift: an average rep on an average day clears it without straining, and the good ones dig for the next $250.

Finally, a data-integrity risk that catches nearly everyone once: spiff and commission dollars often post on a delay or in a different system than the point-of-sale gross profit. If your store-level data pulls hardware and accessory margin from the POS while activation spiffs arrive weeks later in a carrier statement, your grid understates the true gross profit at high-activation stores — which happen to be exactly the stores you should be staffing up. Reconcile the two sources before you trust the grid.

A practical rollout plan

Do not roll this out to the whole chain at once. Wireless retail has enough moving parts that a bad input will discredit the whole method if it lands everywhere simultaneously.

Week one is data assembly. Pull three to six months of gross profit by store and by weekday, and separately pull transaction timestamps bucketed by hour. Reconcile the gross-profit definition against the carrier spiff statements. Compute your chain-wide actual gross profit per rep-day. This week produces no schedule changes — it produces a grid you trust.

Week two is target-setting with leadership. Bring the actual number, propose the target at or slightly above it, and get explicit agreement on which margin layers count. Write the definition down. Every future argument about the number is really an argument about the definition, and having it in writing ends those arguments in thirty seconds.

Week three is a two-store pilot. Pick one store the math says is overstaffed and one it says is understaffed — running only the cut side will teach your managers that this is a cost program. Build both schedules from the division, layer the reps against the hourly curve, and publish. Track gross profit per labor hour, close rate, and accessory attach daily against the prior period.

Weeks four through six are the read. You are watching for the overstaffed store holding or improving its gross profit on fewer hours, and the understaffed store converting more of its existing traffic. If the cut store's gross profit falls roughly in proportion to the hours removed, the store was not overstaffed and your target is too high — adjust before expanding.

From week seven, expand a few stores at a time, and put the recurring cadence in place: monthly schedule recomputation against the rolling three-month average, quarterly review of the per-rep target, and an override log for every store where a coverage policy forced a number the math did not produce.

One tooling note for the rollout: whatever scheduling software your chain uses to publish shifts is downstream of this. Scheduling platforms handle rosters, swaps, time clocks, and multi-site visibility well, and a few will forecast coverage off connected point-of-sale data. None of them will decide your per-rep gross-profit target for you. Do the division yourself — in a spreadsheet is fine — and let the software distribute and publish the answer. The method is portable across every tool; the tool is not a substitute for the method.

Related questions

Should I use gross profit or revenue for this calculation?

Gross profit. Revenue in wireless retail is distorted by device price — a store selling flagship phones on promotional credits can post high revenue on thin margin. Gross profit reflects what the store actually earns and what a rep's day is worth.

How do I handle a brand-new store with no history?

Use the closest comparable location in your chain by format and traffic — kiosk to kiosk, strip center to strip center — and staff to its grid for the first ninety days. Then switch to the new store's own trailing average as soon as you have three clean months.

Does this replace my district manager's judgment?

No. It replaces the default of flat staffing with a defensible starting number. The district manager still overrides for grand openings, competitor closures, training weeks, and coverage policy. The difference is that overrides become visible and logged rather than invisible and permanent.

What if two stores share a labor pool?

Compute headcount independently per store, then assign shared reps to whichever location has the larger unmet gap on a given day. Track hours to the store where the rep actually worked, not to their home store, or your grid will drift.

How does this interact with my rep commission plan?

The per-rep target should be consistent with what a rep must produce to earn a reasonable commission check. If your target sits below the threshold where commission becomes meaningful, you are scheduling people into shifts that cannot pay them, and turnover follows.

FAQ

How do I figure out the right per-rep daily gross-profit target for my chain?

Derive it backward from history rather than picking a number. Take twelve weeks of chain-wide gross profit, divide by the total rep-days worked in that window, and you have your current actual. Set the target at or slightly above that figure. Something around $250 a day is a common starting point for authorized-retailer stores, but your mix, market, and margin stack determine yours. Raise it deliberately as coaching improves; never set it aspirationally high, because the schedule that falls out will structurally understaff you.

What if a store's gross profit swings hard with promotions or new phone launches?

Use a rolling three-to-six-month average so a single launch week does not reset your baseline, and look at the trend line alongside the average. For a known seasonal peak — a major launch, holiday weekends, back-to-school — add temporary coverage as a deliberate override rather than by permanently changing the store's headcount. The rule of thumb: anything that will end in under six weeks gets an override, not a schedule change.

How do I convert a fractional result like 3.6 reps into an actual schedule?

Treat a rep-day as your standard shift length. With eight-hour shifts, 3.6 reps is three full shifts plus roughly a five-hour partial dropped onto the peak window — usually early afternoon through close. Do not round every fraction up; that quietly rebuilds the overstaffing you were trying to eliminate. If your chain runs heavily part-time, redo the whole calculation in rep-hours against a per-rep-hour target and the fractions stop mattering.

What do I do when the math says fewer reps than my coverage policy allows?

The policy wins. If loss prevention or insurance requires two people at open and close, you staff two even when the division returns 1.2. Log it as an override rather than pretending the math produced that number. Those logged overrides accumulate into real information — a location that overrides every single day is telling you it cannot support its own coverage floor, and the answer is reduced hours, consolidation, or relocation.

How often should I recalculate schedules and the target itself?

Recompute store schedules monthly against the rolling three-month average. Review the per-rep target quarterly, since market conditions, product mix, and rep skill all drift. Recalculate immediately and off-cycle when something structural changes — a competitor opens or closes nearby, the mall changes its anchor tenant, or a carrier changes the spiff structure materially.

Can I apply this to a store that also runs a repair bench?

Yes, but compute the pools separately. Repair gross profit and sales-floor gross profit have different per-head economics, so run each against its own target and sum the resulting headcount. The trap is double-counting a technician who also takes sales ups during a rush — decide which pool that person belongs to and count them once, or you will schedule a body you do not have.

Sources

• https://www.bls.gov/ooh/sales/retail-sales-workers.htm
• https://www.bls.gov/oes/current/oes412031.htm
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees
• https://www.dol.gov/agencies/whd/flsa
• https://www.census.gov/retail/index.html
• https://www.nrf.com/
• https://hbr.org/2015/03/the-truth-about-scheduling-software
• https://www.irs.gov/businesses/small-businesses-self-employed/understanding-employment-taxes

Related on PULSE

• How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?
• How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?
• How Do I Score My Retail Managers Across Stores?
• How Do I Get My Cell Phone Store Reps to Attach Accessories?
• How Do I Score Reps at My Multi-Unit Retail Chain?
• RevOps scheduling: matching labor to revenue across locations