Overview

Jonas Club Software includes a POS Partitions feature that lets a club split its point-of-sale operations into separate environments — for example, Golf Pro Shop, Food & Beverage, Tennis, Spa, and Marina. This page explains how partitions work and what they mean for a club's Yellow Dog integration.

For the Retail 2-way API integration, see Jonas API. For the Food & Beverage file export integration, see Jonas File Export.

What Is a Jonas POS Partition

A partition creates a separate POS environment within the same Jonas system. Each partition keeps its own sales items, menus, rules, and operational processes, so POS terminals assigned to one partition can't see items or inventory from another.

Example partition layout for a private club:

Partition Operations
1Golf Pro Shop
2Food & Beverage
3Tennis / Pickleball Shop
4Spa
5Marina

Separating the Pro Shop from the Main Club, for example, prevents Pro Shop users from viewing Food & Beverage items and their related inventory.

What Partitioning Separates

Function Supported
Separate POS item listsYes
Separate menus and sales areasYes
Separate POS rulesYes
Separate departmental inventory visibilityYes
Separate reportingYes
Independent end-of-day processingYes
Different general ledger postingsYes
Separate physical databasesNot established

POS Partitions integrates with Jonas Club Inventory, Club Management, and General Ledger.

Important Limitations

  1. Items cannot be sold across partitions. Sales items and categories belonging to one partition cannot be sold in another.

  2. Partitions are assigned to POS terminals. The partition configuration determines which environment the terminal uses.

  3. Partitions are a separately purchased module. Clubs must license the feature.

  4. Inventory separation is not necessarily database separation. Jonas also supports inventory stock locations and user-group restrictions, but those should not be confused with fully independent databases.

What This Means for Yellow Dog

Yellow Dog offers two Jonas integration paths: the 2-way API (Jonas API) and the 1-way file export (Jonas File Export). Both are configured through the same Jonas interface setup screen, so only one integration type can run per partition — a partition cannot use the API and a file export at the same time. The Jonas 2-Way integration also uses that same interface setup, so the one-integration-per-partition rule applies to it as well.

Practically, this means:

  • A club with separate Golf and F&B partitions needs a separate integration configuration for each partition.

  • Item creation and updates are directed to a specific partition, not shared globally.

  • Whether the same item number can exist across partitions, whether each partition keeps its own unique item identifiers, and whether sales transactions carry a partition identifier are determined per Jonas setup — these are not established by Jonas's public documentation and should be confirmed with Jonas for each client implementation.

Adding a New Partition

Adding a partition is not a self-service change. The club must engage Jonas Professional Services, which typically runs around $1,500 in labor. Build this into implementation timelines and quotes whenever a club's integration design calls for an additional partition.

When an existing partition is split in two — for example, separating Retail from Food & Beverage that currently share one partition — Retail is typically the operation assigned to the newly created partition, with the existing operation remaining on the original partition and its existing integration configuration intact.

Additional Notes

  • One POS integration (API or file export) is supported per Jonas partition — clients running both Retail and Food & Beverage need separate partitions for each.

  • Confirm item-identifier and partition-identifier behavior with Jonas during implementation planning, since these details aren't standardized in Jonas's documentation.

  • See also: Jonas API and Jonas File Export.