Wholesale Handler
CyBake publishes no price, and says why
Most quote-only vendors leave the reason implied. CyBake states it outright on its own FAQ page: it does not publish a guide to prices because every business it serves is different and has its own unique needs, and the way to get a number is to contact them.
That is a real position rather than a dodge - a bakery ERP quote for a single-site wholesale bakery and one for a chain with 30 shops, a production plant and an EDI feed into a supermarket are not the same product. It does mean the sticker price cannot be compared before a conversation, which is the part a buyer pays for in time.
BakeSmart moved the same way in May 2026, pulling most module figures off its public page. BakeSmart pricing records what those modules used to cost before the gate came down.
The four legs of a CyBake bill
CyBake's FAQ page does describe the structure precisely, and this much needs no sales call.
The no-per-user position is not incidental. CyBake argued it publicly in August 2024, calling per-seat pricing a holdover from the era when vendors sold licences to run software on the customer's own hardware, and naming a rival charging $295 a month with $145 for each additional user as the model it rejects. For a growing bakery that is the difference between a bill that tracks headcount and one that does not.
The third-party figures describe a per-seat product CyBake says it is not
Search for CyBake pricing and the numbers that come back are all from aggregators, and every one of them is built on a per-user ladder.
Every one of those ladders is priced per seat, and CyBake's own FAQ says seats are free. The two ITQlick pages contradict each other on implementation by a factor of five. PricingNow's single-user figure is between two and five times ITQlick's for the same seat, and it invents a three-tier plan structure CyBake does not sell.
Aggregator figures like these are templates applied to a software category, not observed quotes. Use them for the order of magnitude - bakery ERP is four-figure-a-year software with a four-figure implementation attached - and nothing finer. What wholesale bakery software costs puts that range beside the vendors who do publish.
What moves the number inside a quote
From CyBake's own description of the model, the variables are the modules and the operation behind them: production planning, recipe management and costing, allergen and nutrition data, lot traceability, stock and purchasing, retail and EPOS, delivery and driver operations, EDI, and accounting integration. A bakery that is wholesale-only skips a large part of the catalogue. A bakery running 30 shops and a plant does not.
Site count, data migration from whatever is being replaced, and training all sit inside the set-up fee rather than the subscription. Why wholesale software is so expensive covers what that implementation work actually consists of.
What stays unknown until the quote arrives
Four gaps that no public source closes.
- The set-up fee. CyBake confirms one exists and publishes no amount, no range and no worked example.
- The module prices. There is no public list of what the core package contains or what each module adds.
- The contract term. No public source states a minimum term, a notice period or a renewal uplift for CyBake. PricingNow's 3-5% annual increase is modelled, not sourced.
- The band you land in. Because the subscription is scaled to the operation, two bakeries of similar size with different module needs can be quoted very different monthly figures.
A quote-only vendor means the number depends on the call - who takes it, what you tell them about your volumes and sites, and which modules the conversation ends up including.
CyBake is bakery ERP, and that is what the money buys
CyBake has been running since 1998 and its production side is not a thin layer. Recipe management with costing, allergen and nutrition compliance, lot tracking and traceability, ingredient stock and purchasing, production reports and picking lists, delivery route optimisation, a driver app with proof of delivery and on-the-spot order amendment, EDI order import and invoice export, EPOS sales-data integration, and multi-site retail. Marks & Spencer runs it across 534 in-store bakeries.
A bakery that needs traceability for an audit, or costs a recipe every time flour moves, is not making a mistake by paying ERP money. It is buying an ERP. Which type of bakery software you need separates that decision from the ordering one.
Order-taking alone does not need a quote
Plenty of bakeries taking an ERP quote need none of that catalogue. A wholesale bakery whose entire bottleneck is orders arriving by phone, text and email from cafes and shops is being priced for production planning it will not open.
Wholesale Handler is that job and nothing else, on a flat monthly price - no set-up fee, no modules, no per-user charge, no commission, and no quote. That covers per-customer price lists, standing orders that refuse a delivery below your minimum spend, cutoff times and accepted delivery days per customer group, delivery charges with a waiver threshold, production schedules with a printable make sheet, packing slips that deliberately carry no prices, processed orders collated into one draft invoice per customer that emails as a PDF when you finalise it, a branded storefront, bulk import and a CSV export of invoice lines. All of it is on the free plan too.
A cheaper alternative to CyBake sets the two side by side feature by feature.
What Wholesale Handler does not do
- Recipes, costing, allergens and traceability. None of it. Stock counting exists, opt-in per product, and it counts finished goods - not ingredients, not lots, not batches.
- Delivery routing and driver operations. No route optimisation, no driver app, no proof of delivery.
- Credit notes. Not built. Adjustment lines can be added while an invoice is still a draft, but a sent invoice is immutable and nothing can be credited against it.
- EDI and EPOS. Neither, so a supermarket that orders by EDI is out of scope.
- Live accounting sync. Invoice line items export as a CSV shaped for Xero and QuickBooks import. There is no two-way integration.
- A second sign-in. One account per merchant today.
Where those matter, CyBake is the more capable product and the quote is worth taking.
