Open Products → Availability Rules using the Sliders Horizontal icon. This screen has no rule name, schedule, date, time, channel, fulfillment-method, priority, edit, or inactive control. Every added rule is active immediately; remove it with the trash control when it should no longer apply.

Before you beginSearch first to avoid duplicate products or reference values. Confirm whether the change is business-wide or location-specific.

Step by step

  1. Open Products → Availability Rules and read the page explanation: Include only makes a location or register sell only selected products or categories; Exclude hides selected products or categories from that scope.
  2. Choose Scope: Location or Register. Changing Scope clears the previously selected location/register so a stale ID cannot be saved under the wrong type.
  3. Choose the exact active Location, or choose the Register shown with its location name. The location list includes active locations; the register list is tenant-wide and labels each register with its related location when available.
  4. Choose Rule: Include only or Exclude. Include only establishes an allowlist for that scope; Exclude establishes a deny rule for the selected target.
  5. Choose Target: Category or Product. Changing Target clears the previous category/product selection.
  6. Choose the Category, or choose the active Product shown with its SKU when present. The product selector loads up to 500 active products ordered by name; if an expected item is absent, confirm it is active and consider whether the catalog exceeds that visible limit.
  7. Choose Add rule. Both a scope ID and target ID are required. CentriPOS saves the rule active immediately and reports Availability rule saved. Re-adding the identical scope, target, and effect updates the same unique rule rather than intentionally creating a duplicate.
  8. Read the rules table after every change. Scope shows Location or Register plus its resolved name; Rule shows Include only or Exclude; Target shows Category or Product plus its resolved name and SKU. Unknown location, register, category, or product means the referenced record can no longer be resolved and the rule should be investigated.
  9. Understand multiple Include only rules as a union. Once any include rule exists for the current location/register context, a product must match at least one included product or category. It does not need to match every include rule.
  10. Understand Exclude as a veto. If a product matches any applicable Exclude product or category, it is unavailable even if it also matches an Include only rule.
  11. At a register, CentriPOS evaluates active rules for both the current location and that exact register together. A match against any applicable include can satisfy the include allowlist, while any applicable exclude still blocks the product. Test combined location and register rules deliberately.
  12. Availability rules are evaluated after the product and each attached category’s own available-location or available-register restrictions. A rule cannot make a product available where the product or one of its categories is already restricted. Product register restrictions take precedence over its location list when register IDs are configured.
  13. In Sell, unavailable products are filtered from the standard product collection, search results, quick-pick grid, remote scanner state, and add-from-quick-pick checks for that operating location/register. These rules do not reduce inventory, deactivate the product globally, or create a fulfillment rule.
  14. For inventory counts, only Location-scoped rules participate because a count belongs to a location rather than a register. Include-only and Exclude use the same union/veto behavior, combined with the product and category’s own location restrictions. Register-scoped rules do not alter countable lines.
  15. To remove a rule, choose the Trash icon at the end of its row. There is no confirmation dialog and no inactive toggle; a successful deletion reports Rule removed and refreshes the table. Resolve the exact row before clicking.
  16. If No availability rules yet appears, the rule table is empty and this layer permits all products. Product- and category-level location/register restrictions can still hide items independently.
  17. Test with one matching and one nonmatching active product in the intended location and register. Check standard Sell search, the product grid, quick picks, and barcode/remote scan behavior. For a Location rule, also begin a controlled inventory count and confirm the countable product scope.
  18. Do not use Availability Rules to manage online-store publication, eCart visibility, delivery eligibility, dates, hours, customer groups, or inventory availability. Use the feature that owns that behavior and describe the intended rule to support if the correct control is unclear.

Screen and contract reference

Control or areaWhat it means
Sliders Horizontal iconNavigation icon for Products → Availability Rules.
ScopeLocation or Register. It determines where the active rule is evaluated.
LocationOne active tenant location selected as the rule scope.
RegisterOne tenant register selected as the rule scope and labeled with its location when known.
Include onlyAdds a target to the applicable allowlist. If any include exists in the current combined scope, a product must match at least one include.
ExcludeBlocks a matching target and always vetoes an include match in the same operating context.
TargetCategory or Product. It determines how the rule matches catalog items.
Category targetMatches products attached to the selected category. A product can match through any of its attached category IDs.
Product targetMatches only the selected product ID, including its variants as part of that product.
Add ruleImmediately upserts an active rule after scope and target are selected. There is no separate Save button.
Rules tableCurrent active and stored rules with scope, effect, target, resolved names, and remove action.
Unknown … labelThe referenced scope or target ID no longer resolves in the currently loaded tenant records.
Include unionA product is allowed when it matches any applicable Include only rule; includes are not an all-must-match intersection.
Exclude vetoAny applicable matching Exclude rule blocks the product even when an include also matches.
Combined register contextSell at a register evaluates both matching location rules and matching rules for that exact register.
Product/category availability boundaryExisting available location/register IDs on the product and every attached category are checked before these rules and cannot be overridden by an include.
Sell enforcementFilters standard Sell products, search, quick picks, remote scanning state, and protected add actions for the current operating context.
Inventory-count enforcementUses Location rules and location-level product/category availability to build countable lines; Register rules do not apply to a location count.
Trash iconDeletes the exact rule immediately, without an inactive state or confirmation dialog.
No availability rules yetNo rows exist in this rules layer; it does not prove every product is otherwise unrestricted.
Not supported hereSchedules, channels, fulfillment methods, online-store publication, customer eligibility, stock quantity, and priority are not controlled on this screen.

Expected result

At the intended operating context, a matching product appears only when it passes its own and every attached category’s location/register restrictions, matches at least one applicable Include only rule when any include exists, and matches no applicable Exclude rule; Sell, quick picks, search, and scanning agree, while a Location rule also produces the expected countable inventory scope without changing stock.

Troubleshooting

  • Confirm whether you are editing a product, variant, shared master record, or location-specific value.
  • Search for an existing product, SKU, UPC, attribute, or tag before creating a duplicate.
  • Preview labels, pricing, and availability in the intended location before broad publication.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.