{"title":"POS objects","slug":"pos-objects","url":"https://support.storeconnect.com/articles/pos-objects","url_markdown":"https://support.storeconnect.com/articles/pos-objects.md","subtitle":null,"summary":"The Salesforce objects behind the StoreConnect point of sale: outlets, registers, shifts, POS users and PINs, layouts, views, action groups, and print templates. Use it to find the right object before you configure or extend a POS.","type":"Developer_Documentation","video_url":"","keywords":"pos objects, outlet, register, register shift, outlet user, pos layout, pos layout field, pos view, pos action group, pos action item, pos print template, printable label, point of sale, data model, salesforce schema","last_modified":"2026-09-15T02:32:04+0000","body_markdown":"The POS objects split cleanly in two: the records that describe where selling\nhappens, and the records that describe what the POS screens look like. Use this\narticle to find the object you need before you configure or extend a POS.\n\n## Outlet, register, shift\n\nSelling is anchored by three records in a chain.\n\nAn [Outlet](outlet-object-reference) is a physical shop. A\n[Register](register-object-reference) is a till within it. A\n[Register Shift](register-shift-object-reference) is one trading session on that\nregister, from open to close.\n\nEvery POS sale belongs to a shift, which is what makes end-of-day reconciliation\npossible: [Register Shift Total](register-shift-total-object-reference) records\nhold the counted and expected figures for the drawer.\n\n:::note\nA POS sale creates the same [cart](cart-object-reference),\n[order](order-object-reference), and [payment](payment-object-reference) records\nas a web sale. There is no separate POS order object. The difference is that those\nrecords point at the register and shift that took the sale.\n:::\n\nWho may operate a POS is set per outlet.\n[Outlet User](outlet-user-object-reference) grants a user access and holds their\nPIN, and [Outlet User Type](outlet-user-type-object-reference) is the role that\ndecides what they may do.\n\n## Screens are configuration, not code\n\nThe second half of this domain is how the POS looks, and all of it is records\nrather than deployed code.\n\nA [POS Layout](pos-layout-object-reference) is a configured screen. Its\n[fields](pos-layout-field-object-reference) say what appears and how, and its\n[filters](pos-layout-filter-object-reference) narrow what it lists. Buttons come\nfrom a [POS Action Group](pos-action-group-object-reference) holding\n[action items](pos-action-item-object-reference). Anything the POS prints is a\n[POS Print Template](pos-print-template-object-reference).\n\nFor the actions an item can invoke, see\n[POS actions reference](pos-actions-reference). For custom Liquid rendered inside\nthe POS, see [POS View](pos-view-object-reference).\n\n## Objects in this domain\n\n| Object | API name | Purpose |\n|--------|----------|---------|\n| [Outlet](outlet-object-reference) | `s_c__Outlet__c` | A physical shop. Holds its address, receipt details, and the stock it sells from |\n| [Outlet User](outlet-user-object-reference) | `s_c__Outlet_User__c` | Grants a user access to an outlet, with their PIN and role |\n| [Outlet User Type](outlet-user-type-object-reference) | `s_c__Outlet_User_Type__c` | A named role at an outlet, controlling what the user may do in the POS |\n| [Outlet Stock Location](outlet-stock-location-object-reference) | `s_c__Outlet_Stock_Location__c` | Sets which stock location an outlet sells and receives from |\n| [Register](register-object-reference) | `s_c__Register__c` | A till within an outlet. Sales, shifts, and receipts belong to one |\n| [Register Shift](register-shift-object-reference) | `s_c__Register_Shift__c` | One trading session on a register, from open to close |\n| [Register Shift Total](register-shift-total-object-reference) | `s_c__Register_Shift_Total__c` | A counted or expected total for a shift, used to reconcile the drawer |\n| [Register Shift User](register-shift-user-object-reference) | `s_c__Register_Shift_User__c` | Records a user working a shift |\n| [Register Fulfillment Category Station](register-fulfillment-category-station-object-reference) | `s_c__Register_Fulfillment_Category_Station__c` | Routes fulfillment work taken at a register to a station |\n| [POS Layout](pos-layout-object-reference) | `s_c__Pos_Layout__c` | A configured POS screen, controlling what appears and in what order |\n| [POS Layout Field](pos-layout-field-object-reference) | `s_c__Pos_Layout_Field__c` | One field shown on a POS layout, and how it behaves |\n| [POS Layout Filter](pos-layout-filter-object-reference) | `s_c__Pos_Layout_Filter__c` | A filter applied to what a POS layout lists |\n| [POS View](pos-view-object-reference) | `s_c__Pos_View__c` | A client-side Liquid view rendered inside the POS |\n| [POS Action Group](pos-action-group-object-reference) | `s_c__Pos_Action_Group__c` | A menu of POS actions, such as a button group on a screen |\n| [POS Action Item](pos-action-item-object-reference) | `s_c__Pos_Action_Item__c` | One action in a group, and what it does when tapped |\n| [POS Print Template](pos-print-template-object-reference) | `s_c__Pos_Print_Template__c` | Markup for something the POS prints: a receipt, a label, or a report |\n| [Printable Label](printable-label-object-reference) | `s_c__Printable_Label__c` | A label definition the POS can print for a product or shelf |\n\n## Where it meets other domains\n\n- **Fulfillment and inventory.** An outlet sells from a stock location through\n  [Outlet Stock Location](outlet-stock-location-object-reference), and work taken\n  at a register routes to a station through\n  [Register Fulfillment Category Station](register-fulfillment-category-station-object-reference).\n  See [fulfillment and inventory objects](fulfillment-and-inventory-objects).\n- **Orders and checkout.** Carts, orders, and payments are shared with the web.\n  See [order and checkout objects](order-and-checkout-objects).\n- **Catalog.** A product must have a price book entry to be sellable at POS, the\n  same rule as the web. See [catalog objects](catalog-objects).\n- **Customers and accounts.** POS operators are\n  [users](user-object-reference), and a POS sale can be attached to an\n  [account](account-object-reference). See\n  [customer and account objects](customer-and-account-objects)."}