Step-by-step instructions
Each taxable order flow has a clear named rule with a percentage, tax type, and saved availability settings.
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
Tax list
How to fill: Start from the list and check existing rows before adding a new tax.
Why: Duplicate tax rules make receipts, reports, and order explanations confusing.
Add
How to fill: Click Add only when you need a new tax rule.
Why: The app creates a draft tax row, so the form must be completed and saved.
Tax title
How to fill: Enter a short, recognizable tax name in the active interface language.
Why: Staff use this label in settings, reports, and order explanations.
Tax title translations
How to fill: Expand the title field and fill every enabled company language.
Why: The value is stored as multilingual JSON in taxes.name and can be shown on multilingual screens.
Tax percentage
How to fill: Enter the exact rate as a number, for example 8.25.
Why: This becomes taxes.procent and is the calculation value for eligible orders.
Tax type
How to fill: Choose Sales tax, Turnover tax, or Value added based on the legal tax model.
Why: The selected type becomes taxes.type and helps reports and agents explain the rule.
Available in orders
How to fill: Select the order flows where this tax should be available.
Why: These choices become taxes.typeorders and control delivery, pickup, dine-in, or catering availability.
Save
How to fill: Save only after title, translations, percent, tax type, and order types are checked.
Why: Unsaved or partially saved taxes cannot be trusted by products, receipts, reports, or automations.
Saved row
How to fill: Return to the list and verify name, percent, and tax type.
Why: The row confirms that the tax rule is ready for downstream setup.
Common mistakes
- Creating a tax draft and leaving it empty.
- Entering a percentage but forgetting to select order types.
- Choosing the wrong tax type for the local tax model.
- Changing a tax rate without checking products, order flows, receipts, and reports that already depend on it.
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 |
|---|---|---|---|
| Tax ID | taxes.id | Unique tax record identifier. | Orders, reports, and support workflows need a stable identifier for the rule. |
| Company | taxes.company | Company workspace that owns the tax rule. | Prevents tax rules from different companies being mixed. |
| Tax name translations | taxes.name | JSON list of tax names by language. | Staff screens, customer-facing text, receipts, and multilingual explanations use this label. |
| Tax percentage | taxes.procent | Numeric tax percentage. | This is the main calculation input for tax on eligible orders. |
| Tax type | taxes.type | Selected category such as sales, turnover, or value-added. | Reports and agents use it to explain what kind of tax was applied. |
| Available order types | taxes.typeorders | List of order flows where the tax can be used. | Controls whether the rule is available for delivery, pickup, dine-in, or catering workflows. |
| Created at | taxes.created_at | Timestamp when the tax row was created. | Useful for audit history and understanding when a tax rule became available. |
| Company include taxes setting | settings.includeTaxes | Whether company prices generally include tax. | Changes how orders explain subtotal, included tax, and final total. |
| Order tax breakdown | orders.taxrates / TaxratesStruct | Tax calculation details stored on orders after a tax is applied. | Agents should read order tax results from the order, not recalculate blindly from the tax list. |
| Product and service assignment | products tax configuration / order flow selection | Where the saved tax rule is later connected to taxable items or flows. | The tax list creates the rule; later screens decide where the rule is actually used. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.