Step-by-step instructions
Receipt settings become clear enough for customers, staff, accounting checks, support review, and later automation that reads receipt behavior from the company profile.
Use the interactive screenshot walkthrough first. Switch steps with the step dots, then read what to fill and why it matters.
Fields on this screen
Automatically print receipt when closing an order
How to fill: Keep enabled when a customer receipt should print immediately after the order is closed.
Why: This prevents staff from forgetting receipts at checkout.
Automatically print production receipts
How to fill: Enable when the kitchen, workshop, bar, or packing station needs a production ticket.
Why: Production receipts separate preparation work from the customer receipt.
Print a receipt copy in the client's language
How to fill: Enable when SABSUS should print customer-facing text in the customer's selected language.
Why: Multilingual businesses can give customers receipts they can actually read.
Print receipt number
How to fill: Keep enabled when the receipt should show a human-readable number.
Why: Customers, staff, refunds, support, and accounting use this number to find the transaction.
Print receipt comments
How to fill: Enable if order comments, delivery notes, or customer requests must appear on the receipt.
Why: Comments help staff and customers understand special instructions attached to the order.
Add customer phone and address
How to fill: Enable for delivery, pickup confirmation, CRM follow-up, or any workflow where customer contact data belongs on the receipt.
Why: The receipt can show who the order belongs to and where it should go.
Print tax totals
How to fill: Keep enabled when the receipt should show total amounts by tax.
Why: Tax totals make the final amount explainable for customers, accounting, and reporting.
Print Wi-Fi
How to fill: Enable only when the business wants guest Wi-Fi credentials printed.
Why: A cafe, bar, salon, or venue can share Wi-Fi without staff repeating the password.
Wi-Fi name
How to fill: Type the exact guest network name, for example SABSUS Guest.
Why: Customers must see the same network name that appears on their phone.
Wi-Fi password
How to fill: Type the current guest Wi-Fi password.
Why: Printing an old or private password creates customer confusion and security risk.
Print predictions
How to fill: Enable if receipts should include a short rotating message, promo, fortune, or visit-again line.
Why: This area can carry customer engagement text without changing product or payment data.
Prediction text
How to fill: Click plus, choose the language, type the customer-facing message, and save it.
Why: The text is stored in the receipt profile and can be shown in the receipt preview.
Print name
How to fill: Enable when the receipt should show a business name block.
Why: A receipt without a recognizable business name is harder to trust and reconcile.
Name source dropdown
How to fill: Open the dropdown and choose Company or Establishment.
Why: Use Company for one legal brand; use Establishment when branches print different public names.
Print address
How to fill: Enable when the receipt should show a business address.
Why: Customers, delivery review, refunds, and tax records often depend on a printed address.
Address source dropdown
How to fill: Open the dropdown and choose Company or Establishment.
Why: Company address fits central operations; Establishment address fits branch-specific receipts.
Print logo
How to fill: Enable when the receipt should include the logo.
Why: Branding makes printed and digital receipts easier to identify.
Logo source dropdown
How to fill: Open the dropdown and choose Company or Establishment.
Why: Company logo is best for one brand; establishment logo is useful for multiple locations or concepts.
Save
How to fill: Click Save only after switches, Wi-Fi text, prediction text, and source dropdowns are checked.
Why: Unsaved receipt settings cannot be trusted by checkout, preview, support, reports, or agents.
Receipt preview
How to fill: Review the preview after saving.
Why: The preview confirms the customer will see the intended name, address, Wi-Fi, prediction, totals, and customer information.
Common mistakes
- Turning on Wi-Fi printing but leaving the network name or password blank.
- Choosing Company as the source when each establishment has its own public name, address, or logo.
- Disabling receipt number printing before confirming how refunds and support will find orders.
- Forgetting to save after typing Wi-Fi or prediction text.
- Checking only the switches and not the receipt preview.
AI Agent Field Reference for implementation
This block is intentionally below the human instructions. It explains storage names and downstream dependencies for automation, support, and future AI agents.
| Field | Stored as | Purpose | Why it matters |
|---|---|---|---|
| Receipt settings object | company.receipt | JSON object saved on the company row. | Checkout, preview, support, reports, and agents read receipt behavior from this object. |
| Automatically print receipt when closing an order | company.receipt.AutoprintafterCloseOrder | Controls customer receipt auto-print after order close. | Prevents missed receipts when staff close orders quickly. |
| Automatically print production receipts | company.receipt.AutomaticPrintingofProductionReceipts | Controls kitchen or production ticket printing. | Preparation stations need their own operational ticket. |
| Print a copy in the client's language | company.receipt.PrintLanguageClient | Controls whether customer-language receipt copy is printed. | Keeps multilingual customer communication consistent. |
| Print receipt number | company.receipt.PrintNumberReceipts | Controls whether the receipt number appears. | Receipt numbers are needed for refunds, lookup, and reconciliation. |
| Print comments | company.receipt.PrintComment | Controls whether order comments appear. | Special requests and delivery notes should not disappear from the printed document. |
| Print customer phone and address | company.receipt.PrintinfoClient | Controls whether customer contact data appears. | Delivery and CRM workflows may need customer identity on the receipt. |
| Print tax totals | company.receipt.PrintSummWithTax | Controls tax total display. | Accounting and customers need to understand tax amounts. |
| Print Wi-Fi | company.receipt.PrintWifi | Controls whether the Wi-Fi block appears. | Guest Wi-Fi is customer-facing convenience, but should be intentional. |
| Wi-Fi name | company.receipt.NameWifi | Guest network name printed on receipt. | The printed value must match the real network. |
| Wi-Fi password | company.receipt.Password | Guest network password printed on receipt. | The printed value must be current and safe to share. |
| Print predictions | company.receipt.PrintPredictions | Controls prediction or promotional text printing. | This adds customer engagement text without touching order totals. |
| Prediction text | company.receipt.Prediction | Array of prediction or promotional text entries. | Receipts can rotate or show short messages in the selected language. |
| Print business name | company.receipt.PrintName | Controls whether a name block appears. | Receipts need an identifiable business name. |
| Name source | company.receipt.PrintNameCompany | Chooses Company or Establishment as name source. | Multi-location companies may need branch-specific receipt names. |
| Print business address | company.receipt.PrintAddress | Controls whether an address block appears. | Customers and accounting often need the address on receipts. |
| Address source | company.receipt.PrintAddressCompany | Chooses Company or Establishment as address source. | Use the source that matches the real seller for the transaction. |
| Print logo | company.receipt.PrintLogo | Controls whether a logo appears. | The logo makes the receipt recognizable. |
| Logo source | company.receipt.LogoCompany | Chooses Company or Establishment as logo source. | Branch-specific brands can use their own logo. |
| Save | CompanyTable.update(company.receipt) | Writes the receipt JSON back to the company record. | Until saved, downstream receipt behavior remains unchanged. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.