Global Retail POS — Day 3 Feature Overview

1. Customers Module & Store Options [00:03:04]

1.1 Customers module in the portal

• The Customers app appears in the Genius app tray and is used to:
  • Create and manage customer profiles.
  • Associate transactions with customers for history and reporting.
  • Enable future CRM/loyalty and customer-level analytics.

1.2 Enabling customer association at POS

• Store-level flag under Store Setup → Store Operations → Business Options:
  • “Allow staff to associate new and existing customers to transactions”.
  • When enabled, the Customer button appears in POS so staff can attach customers to tickets.
• If the customer button is missing in POS, this flag is the first place to check.

2. Item Library, Taxes, Modifiers & Inventory [00:04:40]

2.1 Item Library basics

• Primary navigation: Items → Item Library in the Genius Portal.
• From the library merchants can:
  • Create new items (single, not import-based).
  • Access related configuration: Taxes, Modifiers, Item Alert Messages, etc.
  • Search existing items by name or code.
• Standard item fields:
  • Name, Category, Open item toggle.
  • Unit price (required for non-open items).
  • Cost (optional but required for accurate margin/profit reporting).
  • Optional MSRP.

2.2 Taxes & tax groups

• Taxes are configured per region (US vs Canada) but share a similar structure:
  • Define tax name, rate, and application (e.g., inventory, miscellaneous, receipt settings).
  • When a tax is saved, inventory can be attached directly from the tax screen (if not “all inventory”).
• Taxes can be assigned:
  • At the item level.
  • Via groups applied to many items at once.

2.3 Modifiers & modifier sets

• Modifiers model variations or add-ons:
  • Examples: size, color, gemstones, toppings, add-ons.
  • Each modifier can affect the price positively or negatively.
• Modifier sets:
  • Groups of modifiers that can be attached to items in one step (e.g., “Gemstones”, “Coffee Sizes”).
  • Useful when the same options apply across many items.
  • Support required vs optional selection behavior.

2.4 Inventory tracking & physical counts

• Inventory tracking can be configured to:
  • Track quantity on hand per item.
  • Trigger low-quantity alerts at POS once a threshold is reached.
• Two main ways to adjust inventory:
  • Physical counts: replace existing quantities (full count of what is on the shelf).
  • Item receiving: add quantities to existing on-hand stock (shipment receiving).
• Imports for inventory use the same ODS format as item imports; item IDs must not be changed for existing items.

2.5 Item imports (ODS templates)

• Item imports use an ODS template:
  • Download from the portal; edit in software that supports ODS (e.g., Excel, Google Sheets).
  • Apple Numbers is not supported for this file type.
• Item ID behavior:
  • Generated by Genius when items are first created.
  • When importing the first time: leave Item ID blank — Genius will assign IDs.
  • When updating items: Item ID must be present and unchanged so the import updates the correct records.

2.6 Barcodes & scanning support

• Items with manufacturer barcodes or UPCs can store those values in the Item Code field:
  • Once stored, those codes can be scanned at POS.
• Barcode generation/printing:
  • Genius for Retail does not yet generate barcodes natively.
  • Merchants can use third-party tools to generate barcodes, then import those codes into the item file.

2.7 Order Ahead visibility flags

• Items can be marked as available or not available for Order Ahead:
  • Useful when some products should not appear on the online ordering site.
  • Controlled per-item so merchants can tailor their online menu separately from in-store POS.

3. Discounts & Promotions [01:00:00]

3.1 Discount types

• Discounts appear in POS as options to be applied manually; they are not auto-applied promos.
• Supported structures:
  • Order-level vs item-level discounts.
  • Percentage vs fixed amount.
  • Simple manual discounts (e.g., “Friends & Family 10% off entire order”).

3.2 Restrictions & eligibility

• Discounts can be restricted by:
  • Items or categories (e.g., no discounts on gift cards).
  • Locations (multi-location merchants configure per store).
  • User roles (manager-only “save-the-sale” discounts).
• Eligibility rules can include:
  • Minimum item counts (e.g., BOGO, “buy 3 get 1 free”).
  • Minimum spend thresholds for the order.

3.3 Manager approvals

• High-impact discounts can require a manager PIN:
  • POS prompts for manager credentials when a restricted discount is applied.
  • Ensures control over discretionary or large-value discounts.

4. Item Screens, Categories & Online Visibility [01:10:03]

4.1 Item Screens concept

• Item Screens control the layout of buttons on the POS sales screen:
  • Group items into screens (e.g., Breakfast, Lunch, Jewelry, Stationery).
  • Use categories and subcategories for organization.
  • Define tile colors and icons for quick visual recognition.
• Multiple screens can be defined and assigned to devices or locations as needed.

4.2 Assigning items to screens

• Items are attached to categories, then categories are placed onto item screens.
• Once a category and its items are assigned and the device is synced, they appear as buttons at POS.

4.3 Order Ahead visibility from screens

• Item visibility on Order Ahead menus can be controlled per item:
  • Disable items that should never appear online.
  • Allow others to be both in-store and Order Ahead.

5. POS Home, Sales Flow, Help & Device Settings [01:24:00]

5.1 POS home navigation

• Key buttons on the POS home screen:
  • Sales/Orders: launches the full sales workflow.
  • Quick Sale: amount-only sale, no itemized ticket required.
  • Completed Sales: view historical transactions and start refunds.
  • Admin: opens the POS dashboard page in the Genius Portal.
• Portal access from the device respects:
  • Portal permissions.
  • MFA requirements.
  • Whether the user is allowed to access the merchant portal at all.

5.2 Help and Support

• Help:
  • Available to all users regardless of permission level.
  • Links into the online help center for “how to” articles and procedures.
• Support:
  • Shows contact information (phone, email) and hours of operation.
  • Gives staff a single place to find how to reach support.

5.3 Register settings & peripherals

• Register Settings screen configures:
  • Receipt printers.
  • Card readers (terminals).
  • Barcode/QR scanners.
  • Cash drawers.
  • Order Ahead/online order printers.
• Payment terminals:
  • For countertop setups, an Elo Z30 register pairs with a PAX A920 Classic payment device.
  • Connection uses TCP/IP: configure the terminal’s IP address in register settings.
  • Default port is 10009; normally this should not be changed.
  • The BroadPOS (gateway) app must be running on the A920 and user agreements accepted.
• Printers and drawers:
  • US and Canada use different supported receipt printer models (e.g., Star vs Epson).
  • Cash drawers typically connect through the receipt printer; test functions are available.
  • Online/Order Ahead printers can be separate or share the main receipt printer.

6. Completed Sales, Returns & Refunds [01:40:11]

6.1 Completed sales view

• Completed sales can be searched by:
  • Transaction number.
  • Customer name.
  • Amount.
  • Card last four digits.
  • Date/time.
  • Tender type.

6.2 Return and refund options

• From a completed sale, staff can:
  • Refund the entire sale.
  • Refund selected items.
  • Issue an amount-only refund.
• Refund permissions are set by role; not all users can perform all refund types.

6.3 Card-present refunds

• For card-present transactions:
  • Refunds usually do not require the card to be dipped or tapped again.
  • The system uses stored tokenized data from the original sale.

7. Device & Data Sync Behavior [01:43:08]

7.1 Communication model

• Devices (countertop registers and handhelds) do not talk directly to each other.
• Instead:
  • Each device syncs to the Genius Portal.
  • The portal then propagates updates to other devices at the same location.

7.2 Automatically synced data

• Continuously synced without manual action:
  • Held orders — can be recalled on any device at that location.
  • Completed orders — refunds can be run from any device at that location.
  • User PIN/password changes and lockouts.

7.3 Manually synced data

• Requires a manual sync or logout/login:
  • New items and item changes.
  • New or updated discounts.
  • Tax changes.
  • Item screen layout changes.
• Manual sync is triggered with the Sync button on the POS home screen or by signing out and back in.

8. Connectivity Requirements & Network Setup [01:44:46]

8.1 Handheld connectivity (PAX A920 Max)

• Supports:
  • Wi-Fi.
  • Cellular connectivity with supported SIMs.
• Recommended for a good experience:
  • Roughly 20 Mbps connection or better.
  • Consider using cellular if many devices are contending on Wi-Fi.

8.2 Countertop connectivity (Elo Z30 + A920 Classic)

• Elo Z30:
  • Can use wired Ethernet or secured Wi-Fi (WPA2).
• PAX A920 Classic:
  • Requires 2.4 GHz Wi-Fi network.
  • Must be on the same network as the Elo Z30 to receive payment requests.

8.3 Offline behavior

• Cash transactions:
  • Can be processed while internet is down.
  • Sync back to the portal once connectivity is restored.
• Card transactions:
  • Full credit card store-and-forward is not yet available.
  • Online authorization is required at the time of sale.

9. Ordering Workflow & Deployment (Salesforce) [01:47:39]

9.1 Salesforce business units & plans

• Orders are placed in Salesforce under business units such as:
  • Genius for Retail – US.
  • Genius for Retail – Canada.
• Dealers select:
  • Plan tier (e.g., Essentials, Advanced, Complete; availability varies by region).
  • Hardware form factor (handheld vs countertop).
• US may have bundles (software + hardware); Canada tends to be more a la carte on hardware.

9.2 Information for account build

• Configuration teams use a boarding checklist capturing:
  • Business type (retail vs restaurant) and use case.
  • Tipping method and preferences.
  • Whether cash discounting or surcharging is used.
  • Whether invoicing, Order Ahead and Virtual Terminal should be enabled.
  • Special configurations (identifiers, age rules, etc.).
• Goal is to ship accounts as close to “ready to run” as possible.

9.3 App deployment & hardware shipping

• Typical pattern:
  • Hardware ships within a few business days after order.
  • Application configuration is completed shortly after checklist submission.
• Apps on devices:
  • Countertop (Elo Z30): Genius POS app.
  • A920 Max handheld: Genius POS app + BroadPOS Gateway.
  • A920 Classic (countertop payment device): BroadPOS Gateway only.
• Hardware can be shipped:
  • To the dealer for on-site installation, or
  • Directly to the merchant location.

10. White Glove Setup, Account Build & Dealer Tools [01:52:11]

10.1 Welcome email & credentials

• After account build, merchants get a welcome email with:
  • Account ID.
  • Username.
  • Temporary password.
• On first login they are prompted to set a new password.
• Dealers/admins configure:
  • User roles and access rights.
  • PIN-based POS logins if desired.

10.2 White glove configuration services

• White glove teams can:
  • Set up item libraries, taxes, discounts and item screens based on the boarding checklist.
  • Configure identifiers, age rules and key store settings.
  • Run installation calls and guide merchants through go-live.
• Dealers may still sell their own services while leveraging white glove work behind the scenes.

10.3 Future agency/dealer tools

• Planned agency-level portal capabilities:
  • Single login for multiple merchants.
  • Portfolio view and quick merchant switching.
  • Central tools for building menus, managing configuration and troubleshooting.

11. Q&A & Certification Logistics [01:55:02]

11.1 Dealer enablement details

• Salesforce access:
  • Dealers with existing Genius-for-Restaurant Salesforce access will see Genius for Retail as an additional business unit once enabled.
• Post-training steps:
  • Admin team is notified of dealers who complete certification.
  • Once addenda are signed, the retail business unit is enabled in Salesforce for those users.

11.2 Roadmap Q&A

• Topics addressed include:
  • Future features like nickel rounding (US), vendor management, and purchase orders.
  • Planned additional training sessions as new features launch.