Step-by-step instructions
Orders, staff, storage, payment accounts, delivery, products, receipts, and reports can be separated by branch.
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
List and Add
How to fill: Start from the Locations list and create a new row only when the branch does not already exist.
Why: Duplicates split reports, stock, order history, and customer choices.
Media blocks
How to fill: Upload a real street photo, logo, and location gallery when the branch will be shown to customers.
Why: Customer app cards, public screens, and branded flows depend on these images.
Title and translations
How to fill: Type the short public name, then expand the title field and fill every enabled language.
Why: Staff, customers, receipts, reports, and AI explanations need the same branch identity.
Phone, email, and social media
How to fill: Use public branch contacts, not a private owner contact.
Why: Customers, delivery, support, and notifications need reliable branch-level contacts.
Location type
How to fill: Open the dropdown and choose Store, Restaurant, Bar, or Delivery based on the real workflow.
Why: The type helps SABSUS and future agents decide which order flows and setup checks matter.
Address
How to fill: Open Add address and fill address line, apartment or entrance, city, state, postal code, and country.
Why: Maps, delivery, pickup, taxes, receipts, customer screens, and support depend on the exact address.
Business hours
How to fill: Choose 24/7 only for branches that really work all day; otherwise fill day-by-day hours.
Why: Orders and availability should match real operating hours.
Date, time zone, receipt language, and currency
How to fill: Check these selectors before saving.
Why: Shifts, bookings, receipts, reports, and finance totals must use the correct locale context.
Operational switches
How to fill: Enable only the workflows this branch uses: dine-in, delivery, pickup, catering, kitchen, QR, tables, booking, standard receipt.
Why: These switches show or hide POS and customer app features.
Finance links
How to fill: Connect settlement, safe, cash register, payment methods, stock notifications, tax, service fee, and minimum age.
Why: Payments, cash movements, taxes, reports, and restricted sales need these links.
Advanced options
How to fill: Configure pickup addresses, delivery options, order statuses, IP restrictions, agreements, HTML blocks, order masks, tips, and signing only when the branch needs them.
Why: Advanced blocks affect checkout, delivery, customer app pages, and staff rules.
Save and verify
How to fill: Save only after the visible fields and switches are reviewed, then reopen the row and confirm media and address are present.
Why: Saved establishment data becomes the source for warehouse, workshops, orders, receipts, reports, and agents.
Common mistakes
- Creating duplicate branches instead of editing the existing location.
- Leaving address, time zone, or currency incomplete before enabling orders.
- Enabling delivery, pickup, catering, kitchen, or tables without the matching operational process.
- Using company-wide phone/email when the branch needs its own support contacts.
- Saving without checking finance accounts, tax, service fee, and payment methods.
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 |
|---|---|---|---|
| Available | establishments.available | Whether the branch can be used in SABSUS. | Disabled branches should not appear as active operating choices. |
| Street photo | establishments.street_photo | Storefront or exterior image. | Customers and staff can identify the real physical branch. |
| Logo | establishments.logo | Branch or brand logo. | Shown in customer app, location cards, and branded screens. |
| Location photos | establishments.photo_gallery | Gallery images for the branch. | Helps customers inspect the location before ordering or booking. |
| Title / name | establishments.name | Multilingual short branch name. | Used in navigation, lists, reports, orders, receipts, and AI references. |
| Phone number | establishments.phone | Public branch phone. | Used by customers, support, delivery, and staff communication. |
| Location type | establishments.type | Store, Restaurant, Bar, Delivery, or another branch type. | Controls which workflows and setup checks are relevant. |
establishments.email | Public or operational branch email. | Used for support, notifications, customer communication, and recovery flows. | |
| Social media | establishments.social_medias | Branch social links. | Customer-facing pages can point to official branch channels. |
| Address | establishments.address | Structured location address with map data and address details. | Required for delivery, pickup, receipts, maps, tax context, and support. |
| Business hours | establishments.monday/sunday | Opening windows by weekday. | Controls when customers can place orders and when shifts are expected. |
| 24/7 | establishments.twenty_four_seven | Whether the branch operates continuously. | Prevents accidental day-by-day hour restrictions for all-day locations. |
| Description in app | establishments.description | Customer-facing branch description by language. | Shown in app or public screens and useful for AI summaries. |
| Date format | establishments.date_format_us | American Month/Day or Day/Month date display. | Keeps receipts, bookings, and shift dates understandable for the region. |
| Time zone | establishments.time_zone | Branch time zone. | Orders, shifts, reservations, payroll, and reports depend on correct local time. |
| Receipt language | establishments.language_receipt | Default language for receipts. | Printed and digital receipts should match the branch/customer language context. |
| Currency | establishments.currency | Operating currency for the branch. | Payments, reports, service fees, and order totals must use the right currency. |
| Maximum shift end time | establishments.max_time_finish | Time boundary for shifts that pass midnight. | Payroll and shift reports need the correct operational day split. |
| Fast food mode | establishments.fast_food | Whether fast terminal/order behavior is used. | Changes speed-oriented ordering behavior for quick-service branches. |
| Dine-in | establishments.dinein | Whether dine-in orders are available. | Customer and POS order type choices depend on it. |
| Table management | establishments.work_with_tables | Whether tables/halls are used. | Needed before halls, tables, reservations, and table service flows. |
| Table reservation | establishments.booking | Whether customers or staff can reserve tables. | Controls booking availability for this branch. |
| Delivery | establishments.delivery | Whether delivery orders are accepted. | Delivery zones, fees, taxes, and customer flows depend on it. |
| Pickup | establishments.pick_up | Whether pickup orders are accepted. | Customer checkout and pickup address settings depend on it. |
| Catering | establishments.catering | Whether catering orders are accepted. | Separates catering from ordinary delivery and pickup flows. |
| Kitchen / Production | establishments.production_or_kitchen | Whether the branch prepares items or uses production tickets. | Workshops, kitchen receipts, stock consumption, and preparation flow depend on it. |
| Print QR | establishments.printqr | Whether QR materials can be printed. | Used for table/customer self-service entry points. |
| Standard receipt | establishments.standard_receipt | Whether the standard receipt flow is used. | Checkout and receipt behavior depend on this default. |
| Ask guests | establishments.askguests | Whether guest count is requested. | Useful for dine-in analytics, table service, and service charge checks. |
| Show contact button | establishments.buttonconnect | Whether a contact button appears to customers. | Controls customer support/contact visibility. |
| Automatic delivery taxes | establishments.autotaxdelivery | Whether delivery taxes are calculated automatically. | Delivery totals and tax lines must match the branch tax setup. |
| Show specialists | establishments.specialist | Whether staff/specialists are shown for booking or service. | Service businesses can expose specialist selection. |
| Settlement account | establishments.payment_terminal_account | Account for card or terminal settlement. | Payment reports need the right destination account. |
| Cash collection safe | establishments.safe_account | Safe account for cash collection. | Cash reconciliation and safe balances depend on it. |
| Cash register account | establishments.cash_account | Cash register account for the branch. | Shift cash totals must post into the correct register. |
| Payment methods | establishments.payment_methods | Payment methods available at this branch. | Checkout should only show methods the branch can really accept. |
| Stock notifications | establishments.stock_notifications | Whether stock alerts are enabled. | Managers can be warned before ingredients or goods run out. |
| Notification email | establishments.email_for_stock_notifications | Email for stock warnings. | Alerts need a reliable recipient. |
| Tax | establishments.tax / establishments.taxes | Tax rule links for the branch. | Orders, receipts, and reports need correct tax calculation. |
| Service fee percentage | establishments.service_charge | Branch service charge percent. | Changes dine-in or service order totals. |
| Minimum age | establishments.age | Minimum customer age for restricted branch flows. | Needed where products or services have age limits. |
| Pickup addresses | establishments.localspickup | Pickup points for this branch. | Customer pickup choices depend on it. |
| Delivery options | establishments.typedelivery / deliverysettings | Delivery rules, price, timing, and availability. | Delivery checkout and estimates depend on these values. |
| Order statuses | establishments.statuslist | Custom statuses for branch orders. | Staff and customer tracking use these labels. |
| IP restrictions | establishments.listIP | Allowed IP list for shift registration. | Prevents staff from registering shifts outside allowed networks. |
| Agreement before payment | establishments.productagreement | Language-specific agreement text shown before payment. | Customers can accept branch-specific terms before checkout. |
| Payment link message template | establishments.tamplate | Template text for payment links. | Payment requests should use consistent customer-facing wording. |
| Signing document for orders | establishments.sign | Document/signing configuration. | Required when orders need signed confirmation. |
| Home page: Popular | establishments.popular | Whether popular products are shown. | Customer app home should show relevant blocks only. |
| Home page: Information | establishments.info | Whether information block is shown. | Useful for branch details and customer orientation. |
| Home page: Gallery | establishments.gallery | Whether gallery is shown. | Enable only when useful photos exist. |
| Home page: Banners | establishments.baners | Whether banners are shown. | Controls promotional areas on the branch home page. |
| HTML sections | establishments.html | Language-specific rich content. | Supports detailed public content when plain description is not enough. |
| Order type masks | establishments.dineinmask/pickupmask/deliverymask/cateringmask | Custom display labels for order types. | Customer and staff screens can use branch-specific wording. |
| Tip settings | establishments.tips | Tip type and amount/percent options. | Checkout tips must match the branch policy. |
| Save | establishments row | Writes the branch configuration. | Unsaved data cannot be trusted by orders, stock, receipts, reports, or agents. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.