Independent products
Manage standalone sellable items with their own identifiers, descriptions, prices, costs and eligibility.
PAYBOTX / INVENTORY & OPERATIONS
Not just what you have. What it is. Where it belongs. What it costs. What is committed. What comes next.
Explore the inventory capabilities implemented across our retail POS, liquor-store platform and connected supplier/corporate ERP. The scope labels show where each workflow belongs.
Explore all 80 capabilitiesA WORKFLOW YOU CAN EXPLAIN AT A GLANCE
Select a stage to see how an illustrative supplier order changes physical stock and commitments. A quote does not reserve inventory. Approval does. Shipment releases the allocation and issues the goods.
The quote is under review. No stock is reserved or deducted.
THE COMPLETE INVENTORY CAPABILITY GUIDE
From the core item file to supplier fulfillment and corporate governance. These descriptions are based on the implemented application workflows—not a generic ERP wish list.
80 capabilities across 10 areas
Organize the way you buy, merchandise and sell. Product families stay connected while each physical variation retains its own sellable identity.
Manage standalone sellable items with their own identifiers, descriptions, prices, costs and eligibility.
Group related products under a master. The family is organizational; checkout and physical stock belong to the sellable children.
Connect sizes, colors, flavors and packs to the correct master, while preserving a separate SKU, UPC, price and stock position for each child.
Assign attribute types and shared values to a master and propagate inherited assignments to its active variations.
Create, edit, order, archive or remove attributes and their selectable values. Apply only the attributes relevant to a product.
Place one product in several categories with a primary category, without creating duplicate inventory records.
Organize departments, categories and subcategories. Category colors and display order support a consistent visual register.
Keep master/child and kit/component relationships intact. The editor prevents invalid self-links and incompatible product-type changes.
Give the clerk a short, recognizable description and give the back office the full record. Search and scanning use the same underlying product identity.
Maintain unique SKU and UPC identifiers; a product can retain an internal SKU when no manufacturer barcode exists.
Keep a short description, a detailed description and a compact abbreviated description for space-efficient register carts.
Associate brand names and item images with the product record for inventory lookup, visual selling and portal presentation.
Resolve scans against UPC or SKU. Ambiguous or missing matches stop for correction instead of silently adding the wrong item.
The scan queue processes scans in order; failed scans can be retried or discarded without overwriting subsequent scan work.
Search UPC, SKU, brand and descriptions. Exact identifier matches receive priority; full-text search supports descriptive lookup.
Define unit or weight selling mode, a unit label and scale PLU. Weighted-item checkout accepts the entered measured quantity.
Retrieve bounded product pages rather than loading the entire item file into the register at once. Actual capacity is sized and tested per deployment.
Keep commercial decisions separate from physical stock. Maintain the price structure for different selling contexts and inspect value using the cost basis that matters.
MSRP, selling, member, medical, wholesale, promotional, tier 2, tier 3 and web prices are represented in the inventory model. Exposed fields and checkout selection depend on the store configuration.
Maintain average, last, raw and loaded cost rather than forcing every question through a single cost number.
Multiply each component cost by the quantity required, then total the result for each maintained kit cost basis.
Supplier receiving recalculates average cost using existing on-hand quantity and the cost and quantity of the new receipt.
POS sale lines retain recorded costs so sales-margin reporting can use the cost captured at the transaction.
Choose average, last, raw or loaded cost for applicable inventory valuation and kit reporting.
Restrict cost and liability reporting to authorized users. Inventory lookup and inventory editing can be granted separately.
The shared product model and store-specific operating data remain distinct. Pricing publication and local-price policy are configured for the network.
*Medical pricing and verification apply only to the relevant configured specialty-store model. Bob’s Liquors uses its age-21 workflow, without a medical approval screen.
On hand is not the same as available. Incoming merchandise is not stock already in the building. Keep physical stock, reservations and incoming supply distinct.
The physical quantity recorded at the selected store or warehouse location.
Quantity committed through an order workflow, tracked separately from physical on-hand stock.
Calculated as on hand minus allocated. Incoming on-order quantities are not counted as immediately available.
Track outstanding purchasing quantities and reduce them as merchandise is received through the connected purchasing process.
The same product can have different quantities in each warehouse; a shared catalog does not collapse those balances.
Inventory and purchasing quantities support three decimal places for measured merchandise and component requirements.
Insufficient-stock checks and manager inventory-override records make shortage handling explicit at the register.
Product editing checks whether stock changed while the record was open. Active order reservations cannot simply be erased in the editor.
A kit has a commercial identity of its own, but its availability and fulfillment follow the actual goods behind it.
Assign the kit its own SKU, UPC, descriptions, price, departments and categories, and attach the component assembly.
Specify the product and required quantity for every component. The component list drives calculated cost and buildable quantity.
Buildable kits are constrained by the lowest available-component quantity divided by the required quantity, rounded down to whole kits.
Use product search and the visual product selector to find components while building the kit.
In the supplier ERP, a component kit expands into the separate physical products the warehouse must pick.
The supplier ERP can treat a prepacked, wrapped kit as its own physical stock item rather than pick its components for every order.
Approved supplier orders retain their component requirements and cost snapshots so later catalog edits do not rewrite existing warehouse work.
Applicable stock valuation reports exclude nonphysical masters and component-derived kits so the same physical goods are not valued twice.
Care Kit = 1 device + 2 refills + 1 pouch
Store inventory and supplier warehouse execution share product identity, but serve different operational needs. Move from a location-level balance to an actionable pick location.
Maintain stock positions by warehouse and inspect the location that will supply the order.
Supplier locations carry warehouse, aisle, bin, position, zone and pick sequence, with optional map coordinates.
Transfer available merchandise between configured locations. Source and destination movements preserve the inventory trail.
Assign eligible paid web orders to another configured warehouse before preparation begins, subject to available-stock checks.
Approved supplier orders reserve physical stock against warehouse locations for subsequent picking.
Warehouse views and grouped picking documents organize work around the way the team operates.
Record picked quantities, package references, weights and notes before releasing the shipment.
Entered coordinates support a proximity-based route suggestion; the map is an operational aid, not a surveyed or obstacle-aware routing system.
Illustrative location address. Direct transfers and web-order reassignment operate within configured locations. Cross-database store networks require their connected purchasing/fulfillment configuration; a shared catalog alone does not create a universal stock pool.
See what is selling and what is missing, then create a controlled purchasing path from the store to the supplier and back into stock.
Compare available and on-order quantities with report thresholds and target quantities. Suggested buys account for incoming stock.
Connected store purchasing builds draft demand from eligible paid POS and portal sale lines not already claimed by a prior list.
Include time-bounded supplier suggestions directed to an individual store or the connected network.
Review item quantities, costs and notes before sending the store request to the supplier.
The supplier reviews requests and sends a quote revision; the store approves the specific revision offered.
Order approval checks the configured payment or enabled credit-terms path, including account limits. Demo payment behavior is clearly distinct from settlement.
Receive actual shipped quantities over multiple receipts. Over-receiving and repeated processing are guarded.
Return authorization, store dispatch, supplier inspection, restock or damaged disposition, and credit memos preserve the link to the original order.
Make stock maintenance a controlled activity with a clear record of who changed what—and why.
Start or resume a draft batch, scan UPCs or SKUs and collect item quantities before uploading.
Each recognized scan adds one unit to the draft line. Quantities can be reviewed and adjusted before submission.
Uploading a scan batch adds its reviewed quantities to on-hand stock. It is not an automatic replacement of the store’s existing balance.
Recorded scan-event identifiers protect against processing the same submitted scan request twice.
Print SKU balances with blank count and variance columns for a physical inventory exercise; the report itself does not post stock.
Inspect openings, sales, receipts, transfers, adjustments, allocations and releases with quantity, reference, employee and time context.
Restrict editing, transfers and take-inventory functions by user, while permitting authorized staff to look up stock.
Guarded operational workflows use SQL transactions, authoritative stock reads and audit records to keep changes traceable.
The item file determines more than the selling price. It also controls how a product appears and which customer or fulfillment conditions apply.
Decide which sellable items appear in the customer portal. Product masters do not become purchasable placeholder items.
Maintain item-level pickup and delivery flags alongside the merchant’s customer-approval workflow.
Smoke-shop configurations distinguish unrestricted, age-18, age-21 and medical requirements. Liquor-specific configurations keep the applicable age-21 flow.
Category colors, product images, compact descriptions and prioritized catalog order help clerks browse as well as scan.
Portal orders carry their fulfillment method and approved delivery destination into the store’s preparation workflow.
Track orders through accepted, preparing, ready, out-for-delivery and completed states, with printable order documents.
Item points-per-dollar settings support automatic customer rewards earning, with tier and campaign rules in the loyalty module.
The supplier workflow records carrier and tracking, issues stock at shipment and creates its invoice. Carrier-label purchasing is a separate integration.
Give the network consistent product identity without sacrificing store-level accountability. Headquarters sees the combined picture and can still follow it back to the originating location.
Maintain shared product identity, relationships, categories, attributes and kit components in the corporate catalog.
Supplier catalog changes flow through the cloud publication process to authorized stores.
Choose the store destinations for catalog publication rather than assuming every store always carries every product.
Versioned publication records track store delivery status and support retry of catalog updates.
Each store retains its own operational database; consolidated corporate records retain the source-store identity.
Corporate filters support geography and arbitrary store selections for operational reporting.
Save repeatable management views and return to line-level sales or inventory detail instead of assembling spreadsheets each time.
Produce filtered PDF and CSV outputs for store management, supplier operations and corporate review.
No matching capability. Try a broader term or clear the search.
THE REPORTING LAYER
The 37-report store library includes twelve inventory definitions and six purchasing/transfer definitions, alongside sales, web-order and gift-card reporting. Applicable reports support filters, sorting, paging, PDF and CSV.
Filter the applicable reports by location, date, category, product, staff, vendor or verification requirement. Reorder thresholds are planning inputs; the report does not silently create a purchase order. Supplier ERP adds warehouse valuation, pick documents, shipment/invoice records, returns, credits and receivables reporting.
This guide spans the retail, liquor and Bahama supplier/corporate product family. Not every module is enabled in every installation. Your walkthrough identifies the store configuration, network connections and integrations included in your rollout.
Carrier-label purchasing, direct scale hardware feeds, external payment settlement, payroll-provider submission and outbound messaging require the appropriate provider connection. Serial/lot tracking, expiry-based FEFO, RFID and automatic kit substitution are not represented here as verified capabilities.
There is no fixed merchandising-model limit on the number of SKUs, departments or categories. Actual throughput, storage and availability depend on a deployment sized and tested for your operation.
SHOW US YOUR MOST COMPLICATED INVENTORY QUESTION.