The details behind
a connected store.

Find merchandise by UPC, SKU or description. Browse departments and categories when a shopper brings a question instead of a barcode.

Attach the customer to the ticket, review previous purchases and connect eligible rewards to the sale. Keep history available when helping a returning shopper.

Apply supported line and order discounts with a visible price calculation. Use permissions and reviewable transaction records to protect the economics of the sale.

Sell packaged goods and supported measured items using the configured unit of measure. Scale hardware, precision and weight pricing are confirmed during setup.

Use the existing return workflow and branded receipt tools. Cannabis return requirements include quarantine, package attribution and recorded disposition.

Group related sizes, flavors, colors and packs under a product family. Retain a separate sellable identity and stock position for each variation.

Organize departments, categories, brands, product images and custom attributes. Keep descriptions clear on both a compact register and a customer-facing catalog.

Maintain multiple price fields alongside raw, loaded, last and average cost where supported. Review how the configured selling price affects margin.

Connect a kit to its component products and required quantities. Make availability and cost understandable before staff promise a bundle to a customer.

Choose which merchandise is presented on the register and portal. Bulk editing, validated imports and cannabinoid measurements complete the catalog workflow.

Review on-hand quantities in the configured warehouse or store. Separate the identity of an item from the place where its inventory is held.

Use supported allocation and order workflows to distinguish physical inventory from stock committed to fulfillment. Incoming stock remains separate until received.

Review sales, low-stock information and supplier requirements before purchasing. Plan receiving around the quantities that actually arrive.

Record source and destination movements for supported transfers. Keep the reason and operational context available to the people responsible for the inventory.

Prepare count worksheets, capture scan batches, review counted-versus-expected quantities and approve variances through a defined reconciliation workflow.

Find customers by name, phone or email. Review ticket and item history according to the employee’s access.

Use supported points earning, redemption, tiers and reward campaigns. Keep the balance connected to the transactions that explain it.

Maintain gift-card balances separately from points. Supported sale and redemption flows keep the two kinds of value distinct.

Review prior products while serving the customer and use supported add-to-ticket actions. Store and online history help staff understand the relationship.

Plan follow-up around permission and useful customer context. Include profile merging, retention controls and audience selection in the customer data plan.

Present a searchable catalog with images, categories and product details. Use the supported phone-and-PIN customer access and approval workflow.

Apply the portal visibility and verification controls available in the installation. Cannabis checkout rules follow the selected license and customer requirements.

Bring orders into a dedicated fulfillment queue. Review the items, select supported fulfillment stock and prepare the order for the handoff.

Keep preparation, pickup and supported delivery stages visible. Staff can distinguish an active register ticket from a customer order waiting for fulfillment.

Configure pickup and supported local delivery according to the operating plan. The channel suite also addresses regulated delivery, self-service kiosks and custom storefront interfaces.

Review sales by period, product and customer using supported reports. Compare the patterns that inform purchasing and staffing decisions.

Review stock, valuation, movement and low-stock information. Keep commercial reporting connected to the products and quantities in the store.

Prepare supported PDF and CSV reports for management review. Confirm the included report definitions and filters during the walkthrough.

The wider BOTX platform includes corporate reporting concepts. Define unified cannabis license reporting and cross-store operational controls in the network rollout.

Responsive browser access supports on-the-go review. The analytics suite is designed to extend this view with mobile insight, scheduled reporting and assisted questions.

Use maintained employee records and individual sign-in workflows. Associate supported operational actions with the staff member performing them.

Separate register, customer, inventory, reporting and administrative access. Configure viewing and editing according to the job.

Define who may change prices, handle exceptions or edit sensitive records. Discuss the exact authorization path during implementation.

Use supported clock-in and clock-out tools and review time reporting. Payroll-provider submission is an independently scoped connection.

Retain supported sales, stock and loyalty history for investigation. Cannabis event history and external acknowledgments provide additional context for reviewed workflows.

Scan-assisted check-in captures relevant document fields for staff review, with age and expiration checks and a clear exception path.

Check-in queues help employees see who is waiting, assign service and carry the customer context into the register.

Medical workflow design addresses documentation, validity periods, caregiver relationships and the permissions needed to view sensitive information.

The checkout workflow is designed to recheck the relevant customer and product conditions before completing a transaction, including mixed baskets.

Limit access to identity and medical information, and define retention needs during configuration.

Package records distinguish the retail SKU from the package or batch supplying it. Multiple packages can belong to one merchandise item.

Package receiving covers supplier and manifest references, quantities, units and discrepancy review.

Structured product measurements include usable weight, potency, serving information, laboratory references and expiration details where applicable.

The package workflow is designed to link the quantity sold or returned to its originating package, preserving the operational trail.

Separate sellable inventory, backstock, quarantine, returns and waste through reviewed movements and documented reasons.

License configuration distinguishes the store, license, customer class and inventory rules that govern a transaction.

Purchase-rule design addresses quantity and equivalency calculations across mixed product types, bundles and supported channels. Market-specific validation precedes production use.

Tax configuration addresses product, customer and jurisdiction differences, tax-inclusive pricing, exemptions and reviewable tax breakdowns.

Package-aware labels bring together required data fields, supported printer setup and a history of reprints.

Reporting workflow design covers submission history, pending work, acknowledgments, retries and discrepancy resolution. External reporting connections require separate authorization and verification.

Promotion rules cover scheduled offers, bundles, BOGO-style rules and explicit stacking controls, with eligible products and customer groups.

Weight-price profiles address quantity tiers and measured-product pricing, with consistent rounding and package depletion.

Audience segments connect purchase behavior and customer preferences to consent-aware campaigns.

Digital reward presentation and wallet-pass design connect the member experience to the underlying loyalty balance and transaction ledger.

Campaign measurement is designed to connect eligible offers and communication to response and repeat visits. Provider integrations and message delivery require separate setup.

Supported payment windows present the transaction total and tender choices before staff complete the sale.

Use the supported cash and gift-card workflows selected for the installation. Keep tender history available for reconciliation.

Any live card, bank-payment or terminal connection requires provider approval, technical integration and verification for the merchant’s business and products.

Review original sale references and supported refund records. Provider settlement and cannabis-specific return disposition are independently validated.

Define how the operator compares sales, tenders, provider settlements and exceptions. Bank payments and online prepayment depend on the selected provider and approved merchant configuration.

Each store needs its own sales, inventory, staff and operating context. Shared product definitions should not collapse separate stock balances.

The broader platform supports shared catalog and corporate concepts. Keep cannabis license and jurisdiction boundaries explicit in the configuration.

Discuss the BOTX supplier ERP workflow for requests, quotes, approved orders, warehouse work and receiving handoffs.

Plan the management view around store identifiers, authorized access and meaningful comparisons. Define multi-license cannabis reporting within the agreed network scope.

Validate one operating model before repeating it across a network. Document location-specific requirements, integrations and acceptance criteria.

Self-service kiosk design lets customers browse eligible merchandise and prepare an order, with staff-controlled review and completion.

Channel routing connects the store’s order queue, availability rules and fulfillment ownership.

Delivery controls address service boundaries, eligible addresses, customer verification and the permitted operating model.

Dispatch workflow design addresses driver assignment, delivery progress, documentation and confirmation of the final handoff.

Consumption-lounge workflows are scoped around tabs, service and local operating requirements.

The partner-interface design provides documented access to selected data and workflows, with authorization and explicit limits.

Event delivery, retry behavior and reviewable status help identify a failed handoff between systems.

Menu, accounting, loyalty, delivery and other connections are evaluated individually. Each connection requires a defined implementation scope and applicable provider approval.

AI-assisted reporting and task support are designed around validated business data, role permissions and reviewable actions.

Text-assisted ordering design addresses consent, product eligibility, transaction review and a verified integration path.