Ice Cream & Frozen Yogurt Shop POS: Scoops by Weight, Toppings by Build
Price weigh-and-pay cups without the scale surprises, keep seasonal flavors rotating profitably, move the summer line fast, and sell pints and parties beyond the counter.
The NoPOS developer relations team writes practical guides for building on the NoPOS REST API — from first smoke test to production POS.
Summer Rush: that is the whole reality of an ice cream and frozen yogurt shop. A July evening packs the counter while the crew juggles a weigh-and-pay cup that reads heavier than it looks, a birthday party pickup of twelve pre-packed pints due at six, a kid asking for a dairy-free flavor while the waffle-cone iron smokes, and a manager who needs to know whether the mango sorbet batch paid for itself — while the flavor rails, the topping bar, and the day's cash, cards, and tips land in three different piles. A generic register sees only SKUs and prices, so cups become guesses, seasonal batches become write-offs, and the line melts onto the sidewalk. Build the flow around the scoop — weight or build priced exactly, batches tracked to the pan, and a line that keeps moving at peak heat — and the shop scoops profit all season.
Price cups by weight or by build, never by guess
A heaped cup at a flat price is a margin leak wearing sprinkles. For weigh-and-pay, integrate the scale so the cup weight minus tare flows straight to the ticket at the per-ounce price — no typed weights, no honor math. For scooped shops, price by size with every premium add-in — waffle cone, extra toppings, specialty sauces — as a fixed-price modifier, and make the modifier screen mirror the flavor board so the cashier taps what the customer pointed at. Print the full build on the ticket so the scooper reads flavors and toppings, not shorthand. Cups stop costing you money the week every ounce and every topping has a price.
Track batches to the pan, not the freezer
Dairy, fruit, and premium inclusions spoil fast and cost more per batch than almost anything else in dessert service. Log each batch's exact yield — how many small cups a three-gallon pan of salted caramel actually makes — and count high-cost items daily, not weekly. Handle the shop reality: seasonal flavors with dated runs and sell-by windows, dairy-free and allergen batches kept separate with their own utensils and labels, and over-portioned scoops flagged when food cost creeps past target. Waste stops hiding when the freezer count and the sales count reconcile every close.
Keep the summer line moving while cups stack
The 7 p.m. line dies when every order is a custom tasting flight read one at a time. Split the flow: one screen queues incoming orders in promised-time order, the scoop station sees only the next three builds with full specs, and pickup is sorted by name so families grab and go. Offer saved favorites for regulars — one tap reorders their exact cup — and push pints, cakes, and catering pickups to off-peak windows so the evening scoopers never stop. Throughput doubles when ordering, scooping, and handoff each have their own lane.
Sell pints, cakes, and parties beyond the counter
Pre-packed pints, ice cream cakes, and birthday-party packages are pre-sold revenue — unless the pickup log lives on a sticky note. Sell party packs as dated pickup sequences with deposits at purchase, track remaining pickups per customer, and remind them the day before each pickup window. Require balances collected before the cake box leaves the freezer, and surface expiring holds so staff can nudge redemption instead of writing off melted specials. Prepaid revenue only counts when the freezer side is as disciplined as the sale.
Close the night on yield, melt, and hero flavors
Shop margins hide in heavy-handed scoops, melted pans, and the specialty sundae priced like a single. Track yield per pan, waste per flavor with its cause — over-order versus slow day versus prep error — and margin per build so the hero that always sells gets promoted and the dud that always melts gets cut. Review which toppings actually get tapped and which sit untouched, and rotate the seasonal special onto the board with real batch costs attached. When the recipe, the ring-up, the freezer count, and the pickup all come from the same system, the only thing left to argue about is who gets the last spoonful of cookie dough.
Build from the current contract
Open the gateway for OpenAPI, Swagger, AGENTS.md, llms.txt, and the first X-API-Key smoke test.
More from NoPOS Blog
Bike Shop & Repair POS: Serialized Inventory, Work Orders, and the Spring Tune-Up Rush
Run a bike shop where every frame tracks by serial number, repair tickets move from intake to pickup without sticky notes, and the spring tune-up rush books itself instead of burying the service counter.
Industry GuideCar Wash & Auto Detail POS: Keep the Tunnel Moving, Sell the Membership, Track Every Bay
Run a car wash or detail shop where pay stations and attendants sell in seconds, unlimited clubs renew on their own, and every tunnel pass and detail bay reconciles at close.