> This page is for Documentation. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://fiftytwo-demo.ferndocs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://fiftytwo-demo.ferndocs.com/_mcp/server. # Glossary The API field names use FiftyTwo's own vocabulary rather than generic e-commerce terms. This page is the shortest useful definition of each, with a link to the help-center topic that covers it properly. ## Products and the catalogue | Term | Meaning | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Article** | A sellable product. The atom of the catalogue. See [Articles](/help/store-management/articles). | | **Article group** | The classification hierarchy articles sit in, used for reporting and for group-wide promotions. See [Article groups](/help/store-management/articles-groups). | | **Article list** | An arbitrary named set of articles, independent of the group hierarchy. See [Article lists](/help/store-management/articles-lists). | | **Discount family** | A grouping used specifically for promotions, so a rule can target a set of articles without reorganising the hierarchy. See [Discount families](/help/store-management/discount-families). | | **Label** | A tag on an article allowing a many-to-one relation between articles and a discount group. See [the announcement](/docs/changelog). | | **Department** | A store-level division articles belong to. See [Departments](/help/store-management/departments). | | **Price group** | A set of stores or customers sharing a price level. See [Price groups](/help/store-management/price-groups). | | **View group** | The PLU button layout a shop assistant sees on the till. See [View groups](/help/store-management/viewgroups). | ## Promotions | Term | Meaning | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Campaign** | A time-boxed promotion. See [Campaigns](/help/store-management/campaigns). | | **Discount group** | The rule that defines a discount: which articles are involved and how much comes off. See [Discount groups](/help/store-management/discount-groups). | | **Buy side** | The articles a customer must buy to *trigger* a discount group. | | **Get side** | The articles that *receive* the discount. An article can be on both sides. See [Buy side and Get side](/help/store-management/discount-groups-buyget). | | **Mix discount** | A discount across a mix of articles: "buy any two, get 50% off". | | **Amount discount** | A discount triggered by spend rather than quantity: "spend 100, get 25 off". | | **Discount ladder** | Tiered quantity pricing: "two for 20, three for 29, five for 40". | | **Match discount** | Also called a *discount basket*. Note that Master Data does **not** support discount baskets on the Get side. | | **Coupon** | A redeemable token tied to a discount. See [Discount types](/help/concepts/discount-types). | > **Note** > > Promotions are **store-specific**. The same article can carry different > discounts in two stores of the same chain, which is why [Basket](/api/basket/overview) > takes both a chain and a store in its path. ## People | Term | Meaning | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Operator** | Someone who can sign into a till. Governed by *shop assistant categories*, which define what they are allowed to do. See [Operators](/help/store-management/operators). | | **Salesperson** | Whoever gets credited with a sale, for commission or statistics. Often the same person as the operator, but modelled separately. See [Shop assistant roles](/help/concepts/operator-salesperson). | | **Shop assistant category** | The permission set applied to operators. See [Shop assistant categories](/help/store-management/shopasst-categories). | ## Stores and hardware | Term | Meaning | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Chain** | The top-level organisation. Nearly every API path is scoped by chain number. | | **Store** | One physical location, identified by a store number within the chain. | | **Store group** | A set of stores treated together for master data purposes. | | **Till** | One point of sale. See [Tills](/help/store-management/till-config). | | **Till category** | Configuration profile applied to a set of tills. See [Till categories](/help/store-management/till-categories). | | **SCO** | Self-checkout. See [Self-service checkouts](/help/pos/sco). | | **MPOS** | Mobile POS: ViKING running on a handheld Android device. See [ViKING MPOS](/help/mpos/mo). | | **Emergency POS** | A degraded mode that keeps a store trading when its normal infrastructure is unavailable. See [ViKING Emergency POS](/help/emergency-pos/epos). | | **Store service** | The per-store service that makes a store authoritative for its own trading. See [General server components](/help/store-management/svr-components). | | **EC (enterprise controller)** | The chain-level component that distributes master data to stores. Relevant whenever you POST chain-scoped data. | | **Bpar** | The store configuration utility FiftyTwo consultants manage with your organisation. Master Data schema descriptions reference `Bpar.fieldname` fields. | ## Transactions and money | Term | Meaning | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Transaction POS log** | The record of what happened at a POS. Streamed by [Transaction POS Log](/api/transactions/overview). See [Transaction types](/help/store-management/transaction-types). | | **Receipt** | What the customer is handed. Also the name of the [deprecated API](/api/transactions/receipt-api). | | **Session** | A trading period at a store, used to scope end-of-day reporting. | | **End of day (EoD)** | The close-out report for a store session. | | **Cash statement** | The till's cash count and reconciliation. See [Till management](/help/pos/tillmgt). | | **Balance / bookkeeping** | Reconciliation of a till or operator against expected takings. See [Balance and bookkeeping](/help/concepts/till-balance-book). | | **Credit (account) sale** | A sale billed to a customer account rather than settled at the till. See [Credit sales](/help/concepts/credit-sales). | | **Deposit** | Returnable-packaging deposit, added as its own receipt line. | | **Reverse vending machine** | The machine that takes back empty cans and bottles and issues a deposit redemption slip. | ## Platform names | Term | Meaning | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **52ViKING** | The POS platform. Written simply *ViKING* throughout the help center; previously **52RETAIL**. | | **52 Cloud** | The cloud services and APIs in front of the store estate. | | **52MASTERPRICER** | The suite that [Basket API](/api/basket/overview) belongs to. | | **52LEASING** | FiftyTwo's leasing product. See [52LEASING](/help/leasing/le). | | **52eSELLER SUITE** | FiftyTwo's e-commerce product. See [52eSELLER](/help/eseller/es). | | **ViKING Store Management** | The web application store staff and chain admins use to configure everything above. Most Master Data writes have a Store Management equivalent. | | **ViKING POS Designer** | The tool for designing till layouts, diagrams, and components. See [POS Designer](/help/pos-designer/wpud). | | **Unified commerce** | FiftyTwo's term for one set of rules across every channel. See [Unified commerce](/help/unified-commerce/mp). |