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

The end-to-end process from POS export to published shift

The whole method is a division problem wrapped in about four hours of setup work, and it runs the same way whether you have two corporate-authorized locations or twenty-two. Start by exporting transaction-level gross profit — not revenue — from your point-of-sale or dealer portal for the trailing three to six months. Revenue lies to you in wireless retail. A $1,100 flagship device sale on a two-year installment plan can carry less margin than a $60 case-and-screen-protector bundle plus a port-in activation spiff, so a store that looks huge on revenue can be a labor sinkhole on gross profit. Pull device margin, accessory margin, activation and upgrade spiffs, and any residual or protection-plan commissions into one number per transaction, then roll it up by store and by day of week.

Six months is the right window if your chain is stable; three months is better if you opened a location, lost an anchor tenant, or absorbed a carrier promo change that reset traffic. Strip the outliers before you average — the iPhone launch weekend, the Black Friday door-buster, the hurricane closure, the week the mall's HVAC failed. Those days get their own separate plan, not a seat at the average table. What you want is the boring middle: the ordinary Tuesday, the ordinary Saturday, repeated enough times that the mean means something. Twelve to twenty-four observations per store per weekday is a reasonable floor for confidence.

Now set the per-rep target with leadership, in a room, out loud, so nobody relitigates it in October. Say it plainly to the team: an average rep working an average day should produce no less than $250 a day in gross profit. That's a floor, not a ceiling — your closers clear it before lunch and go digging for the next one. The number itself depends on your economics; a high-margin dealer with strong accessory attach and rich activation spiffs might carry $300–$400, while a low-margin corporate store on thin device spreads might sit at $180–$220. What matters far more than the exact figure is that it's honest, published, and stable for at least a quarter.

Then divide. Store gross profit for that weekday ÷ per-rep target = reps to Schedule. Round with judgment, not with the spreadsheet's default. A quotient of 2.4 in a store with a single register and one back-room fixture is two reps plus a floater from the neighboring location on peak hours; a quotient of 4.6 in a mall kiosk with three transaction stations is five. Fractional results are a conversation about part-shifts and overlapping mid-shifts, not a rounding rule.

Finally, place the bodies against the clock. The count tells you how many; receipt timestamps tell you when. Weight coverage to when activations actually ring — and publish the schedule far enough ahead that predictive-scheduling rules in your jurisdiction, where they apply, don't turn a good plan into a penalty.

Where the schedule creates or leaks revenue

Overstaffing in a cell phone store doesn't just cost payroll — it actively suppresses performance, which is the part most owners miss. Wireless retail is one of the few formats where adding a body can reduce total gross profit. When six reps share thirty ups, each rep touches five customers a day and nobody builds the muscle of working a full queue. Attach rates fall because reps stop bundling — there's another up walking in, and the perceived scarcity of customers makes reps rush the transaction to be first on the next one. Commission plans with tiered accelerators make this worse: split the board six ways and nobody hits tier two, so the whole crew earns at the base rate, morale drops, and your best closer starts answering recruiter calls from the store across the food court.

Understaffing leaks in a more obvious but harder-to-measure way. An activation is a forty-five to seventy-five minute transaction — device selection, credit check, port-in, data transfer, accessory attach, protection plan, and the setup handholding that generates the five-star review. When two reps are each buried in a seventy-minute port-in and three customers walk in at 5:40 p.m., you don't lose one sale, you lose the highest-intent sales of the day. After-work traffic is disproportionately transactional: those people drove there to buy, not to browse. A walked customer in a phone store often doesn't reschedule — they drive to the carrier corporate store two exits down, or they finish the upgrade in the carrier app that night, and the activation credits to a channel that isn't yours.

The leak also runs through the back door: unattended queue time. In a store with a wait, one rep working the floor as a greeter — qualifying, starting the credit application on a tablet, staging the accessory pitch — often produces more incremental gross profit than a second full closer. That's why the raw quotient from your division isn't always a homogeneous count. Five reps might mean four closers and one qualifier on Saturday, but five closers and no qualifier on a Tuesday when there's no line to manage.

There's a third, quieter leak: mismatched skill coverage. A store scheduled to the right headcount but staffed entirely with sixty-day reps will convert business accounts and complex port-ins at a fraction of the rate a tenured rep does. Business and government lines, prepaid-to-postpaid conversions, and multi-line family adds carry the fattest margins in the format and require the most experienced handling. Blend your Schedule so every peak block has at least one rep who has closed a five-line port-in without help. This is the same principle a mattress chain uses when it protects weekend afternoons with its best closers, or a jewelry store uses to guarantee a certified appraiser is present during evening engagement traffic — the count and the composition are two separate decisions, and only the first one comes from arithmetic.

Concrete numbers, benchmarks, and how to sanity-check them

Run the division across your whole footprint and the pattern usually looks something like this. A mall kiosk averaging $1,250 gross profit on Saturday, at a $250 target, needs five reps. That same kiosk on a Tuesday might average $400 — that's two reps, and the second one exists mostly to cover the lunch break and the bathroom, not because the traffic demands it. A strip-center store next to a grocery anchor might invert the curve: $500 on Tuesday, $900 on Saturday, because grocery co-tenancy pulls steady weekday traffic and its Saturday spike is groceries, not electronics. An outparcel store on a commuter corridor peaks hard from 4:30 to 7:00 p.m. Monday through Thursday and dies on Sunday. Same brand, same signage, three completely different staffing shapes.

Convert your target into an hourly figure for a sharper tool. A $250-per-day target across an eight-hour shift is roughly $31 in gross profit per rep hour. That metric — gross profit per labor hour — is what you should actually be reviewing weekly, because it survives shift-length differences, part-timers, and split shifts in a way a per-day number doesn't. Set a floor, a target, and a stretch band. If a store's GP-per-labor-hour is running well under the floor for three consecutive weeks, it's overstaffed or under-trained, and the schedule is only one of those two problems.

Labor as a percentage of gross profit is the second sanity check, and it's the one your P&L cares about. Take total store labor cost for the week — wages plus payroll tax plus commission, at fully burdened rates — and divide by total store gross profit for that week. Most owner-operators in high-margin retail formats want that ratio comfortably under half, and get nervous as it climbs toward it. Wireless is commission-heavy, so a chunk of your labor cost is variable by design and scales with the very number it's measured against; that's a feature, and it means your fixed base-wage exposure is what actually needs the schedule discipline. Model the ratio at three staffing levels for a representative store before you commit chain-wide.

Add cover on top of the raw quotient — always. A five-rep Saturday isn't five people scheduled; it's five on the floor at peak, which usually means six bodies on the schedule once you account for a staggered lunch, a fifteen-minute break, and the reality that somebody calls out roughly one shift in twenty. Build a fixed cover factor of about ten to fifteen percent into the total weekly hours, held centrally at the district level rather than sprinkled into every store's schedule, so a district manager can flex a floater to whichever location gets hit.

For the hourly overlay, pull receipt timestamps and bucket them by hour. Most phone stores show a small lunch bump around noon to one, a genuine trough from two to four, and the real peak from four-thirty to seven on weekdays. Saturdays run broad from eleven to five with the fat part in the early afternoon. Sundays, where you're open, are usually a two-rep day regardless of what the division says, because the traffic is thin and browse-heavy. Staff the opening hour with one person doing inventory counts, display resets, and the online-order pickups, and build the crew toward the evening rather than carrying a full floor at 10 a.m. so everyone can watch the mall wake up.

One more benchmark worth tracking: transactions per rep hour, alongside gross profit per rep hour. If GP per hour is fine but transactions per hour are low, you're winning on a few fat deals and starving the accessory business. If transactions are high and GP is low, you're activating without attaching, which is a coaching problem the schedule cannot fix.

Pitfalls that quietly break the model

The most common failure is scheduling to revenue instead of gross profit. It feels equivalent and it isn't. Two stores at identical revenue can differ by forty percent in margin depending on device mix, upgrade-versus-new-line ratio, and accessory attach. Schedule to revenue and you'll consistently overstaff the high-volume, low-margin location and starve the small store that quietly prints money on accessories and prepaid.

The second pitfall is letting the per-rep target drift. Someone raises it to $300 during a strong quarter to justify a headcount cut, then quietly drops it to $200 in a slow one to protect a friend's schedule. Now the number means nothing and nobody trusts the output. Set it, publish it, and revisit it on a fixed cadence — quarterly, with the same seat at the table each time. If the market genuinely changed, change the target explicitly and tell the whole chain why.

Third: averaging away the shape of the week. An owner who computes one weekly gross-profit figure per store and divides by five days will overstaff Tuesday and understaff Saturday every single week, forever. The whole point of the method is that it's per-store *and* per-day. This is where a lot of otherwise-solid operators get lazy, because per-day requires actually pivoting the data.

Fourth: ignoring the promo calendar. Carrier promotions, launch cycles, back-to-school, and tax-refund season move the curve so hard that a trailing average built through them will mislead you for weeks afterward. Keep an event overlay separate from your baseline. When a launch lands, staff to the launch plan, not the model — and don't let those days pollute next quarter's average.

Fifth: treating the count as a schedule. The division gives you a headcount, not a roster. You still need shift start times, break coverage, skill mix, open and close assignments, and swap handling. Owners who stop at the quotient end up with five reps all scheduled 10-to-7 and a dead store at 6:45 p.m. when the last customer of the day walks in.

Sixth, and this one bites multi-unit operators specifically: optimizing each store in isolation. In a Multi-unit chain, the right answer for the district is often a shared floater pool, cross-trained reps who cover two nearby stores, and a deliberate decision to slightly understaff a low-margin location so the high-margin one is never short at 5:30. Solve the district, not the store. A RevOps lens helps here — you're allocating a constrained resource across a portfolio to maximize total contribution, which is the same problem as territory design or SDR-to-AE ratios, just with floor space instead of accounts.

Seventh: compliance blind spots. Predictive-scheduling ordinances in some cities require advance notice and pay premiums for last-minute changes; minor-hour rules constrain your part-time high-school closers; and overtime creeps in when a district manager patches holes with the same reliable rep every week. Check your local rules and build the constraint into the schedule rather than discovering it in a claim.

Finally: never adjusting. The model isn't a one-time calculation, it's a loop. Review GP per labor hour weekly, re-pull the trailing average monthly, and revisit the per-rep target quarterly.

Choosing the tooling that carries the method

You need two capabilities and they rarely live in one product: the math that converts gross profit into a headcount, and the rostering that publishes shifts, handles swaps, tracks time, and keeps you compliant. Most owner-operators run the first in a spreadsheet or a purpose-built calculator and the second in a scheduling app. That's a perfectly good architecture — don't buy a platform to avoid a pivot table.

Evaluate scheduling tools on four things. First, pricing model versus your crew shape: per-user pricing is cheap when every store runs two or three reps and expensive when you're deep-staffed, while per-location pricing inverts that. Second, whether it can ingest POS or sales data and propose demand-based coverage, or whether you'll always feed it the headcount yourself — both are fine, but know which you're buying. Third, multi-site reporting a district manager can actually read side by side, because comparing eight stores in eight tabs is how the discipline dies. Fourth, the boring operational stuff: mobile publish, swap requests, time clock, overtime alerts, and labor-versus-sales tracking.

Run a two-store pilot for four weeks before rolling anything chain-wide. Measure gross profit per labor hour and labor-as-percent-of-gross-profit at both pilot stores against two matched control stores. If the pilot doesn't move either number, the tool isn't the constraint — your target, your data quality, or your coaching is.

PULSE publishes a free [Rep Scheduling Matrix](/tools/rep-scheduling) that runs this division across every store and day at once in the browser, which is the fastest way to Figure out honest per-day counts before you commit to any subscription. It's a calculator, not a roster — pair it with whatever scheduling app fits your crew shape.

Related questions

What if a store's quotient comes out below one rep?

You still can't run a store with half a person. That location is either a candidate for reduced hours, consolidation into a nearby store, or a strategic loss-leader you keep for market presence. Make that call explicitly rather than letting the schedule quietly bleed.

How often should I re-pull the trailing average?

Monthly for the rolling window, quarterly for the per-rep target. More frequent re-pulls chase noise; less frequent and you'll miss a real traffic shift — a new anchor tenant, a competitor opening, a carrier promo change — for an entire season.

Does this work for a single store?

Yes, identically. Drop the store dimension and run the division by day of week only. The per-day shape matters just as much for one location; you simply lose the district floater pool as a lever for absorbing variance.

Should commission-heavy reps change the target?

The target is gross profit produced, not wages paid, so it doesn't change. But a commission-heavy plan means your labor cost scales with performance, which lowers the risk of a slightly generous headcount and makes the labor-as-percent-of-gross-profit check more forgiving.

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

Use a comparable store's curve — similar format, traffic pattern, and co-tenancy — as the starting model, staff slightly heavy for the first six weeks to protect the grand-opening experience, then switch to the store's own data as soon as you have twelve clean observations per weekday.

FAQ

Why gross profit and not revenue or foot traffic?

Revenue overstates low-margin device volume and understates accessory and activation income, so it routinely misallocates labor between stores. Foot traffic counts browsers identically to buyers. Gross profit is the only input that reflects what a rep's presence is actually worth on that floor on that day.

What's a reasonable gross-profit-per-rep-per-day target?

It's entirely dependent on your margin structure, so there's no universal figure. $250 a day is a common working starting point for an average rep on an average day; dealers with rich accessory attach and activation spiffs may set it higher, thin-margin corporate formats lower. Set it from your own trailing data, publish it, and hold it for a quarter.

How do I schedule the hours within the day once I know the count?

Bucket your receipts by hour over the same trailing window. Open light — one rep handling inventory, resets, and online pickups — build through the lunch bump, hold through the early-afternoon trough, and peak your crew from roughly four-thirty to seven on weekdays and through the early afternoon on Saturdays.

Do I need scheduling software, or is a spreadsheet enough?

A spreadsheet is genuinely enough for the math at almost any size. What software buys you is publishing to phones, swap handling, time and attendance, overtime alerts, and multi-site visibility for district managers. Below roughly five stores, plenty of owners run the math in a sheet and the roster in a cheap app.

How do I keep the model from breaking during a device launch?

Keep launch weeks in a separate event plan with its own staffing, and exclude them from the trailing average that feeds your baseline. Launches are a queue-management problem — greeters, appointment slots, pre-orders — not a gross-profit-division problem.

Does this method transfer to other retail formats?

Yes, wherever a transaction has meaningful margin variance and a salesperson materially affects conversion — mattress, jewelry, furniture, powersports, appliances. It transfers poorly to formats where labor is driven by throughput or task load rather than selling, such as quick-service food or grocery, where you schedule to transaction counts or production volume instead.

Sources

• U.S. Bureau of Labor Statistics — retail salespersons occupational data: https://www.bls.gov/ooh/sales/retail-sales-workers.htm
• U.S. Small Business Administration — managing business finances: https://www.sba.gov/business-guide/manage-your-business
• U.S. Department of Labor — Wage and Hour Division: https://www.dol.gov/agencies/whd
• National Retail Federation — retail industry research: https://nrf.com/
• Harvard Business Review — operations and workforce management: https://hbr.org/
• IRS — business expenses and cost of goods sold: https://www.irs.gov/businesses/small-businesses-self-employed
• SCORE — small business mentoring and templates: https://www.score.org/
• MIT Sloan Management Review — operations research and management: https://sloanreview.mit.edu/

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)
• [How Many Staff Should I Schedule Each Shift at My Sushi Restaurant?](/knowledge/tl0094)
• [How Many Employees Should I Schedule Each Shift at My Pottery Studio?](/knowledge/tl0007)