Bakery and confectionery user guide

Create your account

Sign up with Gmail and confirm the email code, or use Google when configured. Select Bakery and confectionery and your branch. The trial starts automatically.

Set up the business and payment

Review tax, payment methods, receipt details and staff discount limits in Settings. Test the printer on the device that will use it.

Items and prices

Add categories, names, prices and the correct units. Example: A 2 kg cake with a deposit and pickup date. For imports, download the template and test a small set first.

Staff accounts and sign-in

The owner creates each employee account and assigns a role and branch. Staff sign in with a phone number and password, or a PIN on a trusted device. No phone verification code is required. The owner manages staff password recovery.

Sell by piece or weight, record cake deposits and pickup dates, and follow production.

1. Record items and quantities

   Set up the required items, prices and customer details before confirming.

2. Book the order and deposit

   Record the actual status, quantities and any payment, using the appropriate screen.

3. Hand over and settle the balance

   Check the final bill, payment method and remaining customer balance.

Payments and shift closing

Check the payment method before confirming the bill. At shift end, count actual cash and submit it in Shift. Managers review differences according to permissions. Start returns from the original invoice and record a reason.

Owner follow-up

Start with the dashboard, then filter reports by period and branch. Sales, collections, costs and returns have different meanings. A credit sale does not mean cash was received today.

Trial, subscription and branches

Review the duration, price and active branch count in Subscription before requesting payment. The main branch starts automatically at signup. Only the platform administrator can add, edit, activate or deactivate branches. Contact support for an additional branch and its price. Branch prices apply per active branch. Pro activation does not itself record a payment. Available features depend on the plan and permissions.

Working during an internet outage

Open checkout online first. Supported transactions wait in this device’s local queue during an outage. Review synchronization after reconnection. Do not clear browser data or manually repeat pending sales. Approval and balance checks still apply.

Preorders and deposits

Record items, quantities, customer, pickup date and notes. Collect the actual deposit. Mark the order ready, then review the available credit and final invoice at pickup.

Production and waste

Record the actual prepared quantity and check ingredient or stock movements according to item setup. Record waste with a reason and review the day’s movements.

Delivery and collection

Check the customer, address, zone and fee. Assign a driver when used, update delivery status, and reconcile money actually collected.

Ingredients and recipes

Configure ingredient units and recipe quantities where used. Review receipts, waste and stock counts. Recorded cost is required for meaningful profit reports.

Selling units and conversions

Set a base unit and each conversion factor. Test one sale and check the stock movement before using the configuration widely.

Selling by weight

Configure the weight unit and its price. Enter actual weight or use the device’s configured scale, then review quantity and total.

Wholesale and customer prices

Configure wholesale or customer-specific prices. Select the customer before payment and review floor prices and discount permissions.

Price quotes

Prepare items and prices for a named customer and set validity. Convert an agreed quote to a sale and review payment. A quote is not a paid invoice.

Online orders

Review the public link, offered items and settings in Online. Confirm incoming orders and follow the workflow for your activity. Online payment needs its own configured account.

Customer credit and outstanding balances

Customer credit is shared across their transactions; a deposit is not automatically reserved for one ticket. Credit sales require an identified customer, an allowed limit and an enabled method. Record collections in the customer account.