Cell Phone Shop POS: Repairs, Trade-Ins and Carrier Activations

A cell phone shop earns money from four different places: devices, accessories, repairs and carrier activations. A POS for that shop has to keep those four lines apart, because they have different margins, different timing and different risks. This guide covers three of them that general retail software handles poorly: repairs, trade-ins and activation income. It also says plainly which parts Retailer OS handles and which it does not.

How should a phone shop track repairs in a POS?

A repair ticket is a record that follows one device from drop-off to pickup: who owns it, what is wrong, what you quoted, which parts you used and what the customer paid. A normal checkout cannot do that, because a repair is a promise that stays open for hours or days.

Whatever system you use, a repair ticket should hold these fields:

• Customer name and phone number, so you can reach them.
• Device make, model and serial or IMEI, written at drop-off and checked at pickup.
• The fault as the customer describes it, and the fault you found.
• The quote, any deposit taken, and the final price.
• Parts used, with cost, so each repair has a real margin.
• Status: received, diagnosed, waiting for part, ready, picked up.
• Warranty length on the repair, and the date it ends.

Do not store a customer's passcode in the POS or anywhere a second person can read it. Hold it only as long as the job needs it, or ask the customer to turn the lock off for the repair.

Know the margin on each repair type. Take a $129 screen repair. The part costs $42. A technician spends 30 minutes at a loaded labor cost of $20 an hour, which is $10:

Be clear about what Retailer OS does here. It is not a dedicated repair-ticket system. It does not manage a status board, parts-on-order tracking or customer pickup alerts for phone repairs. If repairs are the center of your business, test a repair workflow in any POS you are considering, and ask us in a demo how repairs would work alongside Retailer OS.

What it does have is useful around the edges: customer profiles with purchase history, so you can see the original sale when a warranty question comes up; appointment booking for drop-offs; discounts and price overrides under role permissions; and an inventory ledger with cost for the screens, batteries and charge ports you stock. Texting a customer that a phone is ready needs a Messaging & AI plan (Starter $39.99, Growth $69.99 or Pro $99.99 a month).

How do you handle trade-ins at a phone shop?

A trade-in is a used device you buy from a customer, paid in cash or store credit, that you then refurbish and resell or sell on to a wholesaler. It is inventory with a cost, not a discount, and it needs its own record. The steps for a safe trade-in are the same in any shop:

• Check the customer's ID and record who sold you the device. Secondhand dealer rules vary by state and city, so check what applies to you.
• Confirm the lock status. The device must be signed out of the owner's cloud account, or you cannot resell it.
• Check the serial or IMEI against a blacklist lookup, since a device reported lost or stolen is a loss to you.
• Grade the condition (for example A, B or C) using the same written standard every time.
• Set the offer with a formula, not a feeling.
• Pay and record it with the serial number and cost attached to the device.

The offer formula keeps a good trade-in from becoming a bad deal:

Retailer OS has no trade-in appraisal or buy-back flow, and does not run blacklist lookups. What it supports is the record afterward: serial-number tracking on items, variants for storage size and color (you can add condition as another variant), cost tracking, and store credit and gift cards as tender. A trade-in paid as store credit can be applied to the next purchase, and it tends to bring the customer back. Keep used devices as separate items from new ones so a refurbished phone never gets sold as new stock.

How should you track carrier activations and commission income?

Activation income is money a carrier pays you for signing up a customer. It is not money the customer pays at your counter. That one difference breaks how most shops count it.

Carrier commissions arrive later, on the carrier's schedule, and they are often reduced by a chargeback if the customer cancels within a set period. So the commission you see on the day of the activation is a forecast, not revenue. Treat it as its own income line, separate from device and accessory margin.

Retailer OS does not connect to carriers, and we do not claim any carrier integration. Commissions come from the carrier's statement, so record them in your accounting software as their own income account, and reconcile the carrier statement against your activation log each month. Retailer OS sends a daily sales journal per channel to QuickBooks Online (QuickBooks is the accounting side), and the carrier payments are entered there directly.

Count the labor you spend on each activation, because it can be longer than you think. If a typical activation takes 40 minutes at $18 an hour, that is $12. Take a $50 commission with a 20 percent chargeback rate:

If you take bill payments or collect activation fees on a carrier's behalf, keep that cash separate in your records and reconcile it on its own, so your register sales stay clean.

What should the counter and drawer routine look like?

Phones are small, expensive and easy to resell, so the counter routine has to be tight. Three habits do most of the work. Our earlier guide to phone shop serials, accessories and theft control goes deeper on theft, and the electronics guide on serial numbers, warranties and shrink is a useful companion.

• Count serialized devices every day. Count by serial number, not by model, so a swapped phone shows up.
• Count accessories by category every week. Cases and cables are small enough to leak in volume.
• Close the drawer every shift. Retailer OS shows what the drawer should hold, you enter counted cash and a note, and the variance is recorded.
• Limit who can discount a device or override a price. Retailer OS treats discounts, price overrides, voids and refunds as separate permissions.
• Read the cashier performance report for unusual voids or refunds by person.

The attach rate on accessories is worth a weekly look as well. Attach rate is accessory sales divided by device sales. If you sold 40 phones and 52 cases, your case attach rate is 130 percent, which means some phones sold with more than one. If it drops to 60 percent, your counter staff have stopped asking. Retailer OS sales and top-products reports give you the inputs.

What does Retailer OS handle for a phone shop?

• Counter checkout: barcode scanning, mixed tenders, split payments, returns, exchanges and receipts by print or email.
• Serial-number tracking on items, plus variants for storage and color.
• Inventory ledger: per-item stock with a movement row for each sale, receipt, transfer and adjustment, plus reorder points and alerts.
• Purchase orders and receiving with cost tracking for parts and devices.
• Customer profiles, loyalty and appointment booking.
• Roles, audit log and drawer close.
• Card readers: Stripe Terminal readers with tap, insert and swipe, on your own Stripe account.

If you run a kiosk in a mall, note that offline selling works in the desktop app only. The iOS app has no offline mode, so plan your hardware around where your internet is least reliable. Details are on the platform page.

Pricing is per store and per user seat: $99.99 a month for a store and $9.99 a month per user. One shop with three staff costs $99.99 plus 3 × $9.99, which is $129.96 a month. Retailer OS takes no platform fee and no cut of sales, and Stripe charges its processing fees directly. The pricing page lists the optional add-ons.

What should you ask any POS vendor before you buy?

• How do I keep a repair open for several days with a deposit and a balance due?
• Can I record parts used on a repair against stock at cost?
• Can a used device be tracked by serial number as a separate item from new stock?
• Can I pay a trade-in in store credit and apply it to the next sale?
• How should I record carrier commissions that arrive weeks after the sale?
• Can I limit device discounts and price overrides to managers?
• How does it run when the internet drops, and on which devices?

Write down the answers. A vendor who says "we can do that" without showing it is giving you a hope, not a feature.