Using this glossary: Terms are organized alphabetically. Click on any term to jump to its detailed article.
| Term | Definition |
|---|---|
| Activity Logs | An immutable record of every authenticated request that touched your account, logged as Read, Create, Update or Delete — capturing what happened, who did it, when, and which record it affected. Reads are included, so opening a record leaves an entry. Activity logs are compliant for audit and regulatory requirements; retention depends on your plan. |
| Attributes | An attribute is a custom field you define to capture information TWICE does not have a built-in field for — specifications, operational data, business metadata. Attributes attach to inventory, catalog, customers and orders, and can be typed, masked, grouped and used in filters and formulas. |
| Attribute Groups | Named collections of Attributes that drive how the Attributes tab is sectioned on entity detail pages. |
| Category Taxonomy | A standardized hierarchical product classification system that organizes inventory into categories and subcategories. TWICE uses the Shopify Product Taxonomy standard to ensure consistent categorization across your catalog and integrations. |
| Checkout | A Checkout collects payment for a cart or an order. On the storefront it starts from the customer's cart and creates the order when it completes; from the admin or a checkout link it is opened against an existing order. A checkout can carry several payments, which is how partial payments work. |
| Collection | A Collection is a curated group of listings organized for merchandising and navigation purposes. Collections help customers discover products by category, theme, or business logic, and can be displayed across your online store and sales channels. |
| Customer Tag | A customer tag labels a customer profile so you can group and filter customers — wholesale, VIP, staff. Tags drive segmentation and filtering; they do not by themselves change pricing, and there is no per-tag pricing on a Price Table. |
| Customer Profile | A Customer Profile is the record of an individual or business customer, holding contact details, addresses, language and marketing consent, order history, attached documents, and any attributes you have added. |
| Event | An event is an entry on a stock item's timeline. Orders the item is assigned to appear there and block availability; reservations block availability without an order; notes record something without blocking anything. |
| Input Mask | A template string on a text Attribute describing the exact shape a value may take — # a digit, @ a letter, * either, […] an optional ending, everything else fixed text. A value must match one of the Attribute’s masks. |
| Income & Expenses | Per-record history of value changes — initial value, updates, and depreciation — captured as immutable entries on the Income & Expenses tab. |
| Integrations | Integrations connect TWICE to the rest of your stack through the Admin API, API keys and webhooks — headless storefronts, accounting, automation platforms, and your own backend. |
| Inventory Tracking (Pooled) | An inventory record covering several identical stock items (quantity above 1) under one set of item codes. Income, expenses and timeline events are aggregated across the record — you see the total, not what happened to any one item. |
| Inventory Tracking (Serialized) | An inventory record covering exactly one stock item (quantity 1), with its own item codes, income, expenses and event timeline. This is what lets you see what happened to one specific item. |
| Inventory Record | An inventory record is the row that holds your stock. It covers either one stock item (quantity 1) or several identical stock items tracked together (quantity above 1). Item codes, condition, income and expenses, and the event timeline all belong to the record, so a record covering several items reports them together rather than one by one. |
| Line Item | A line item represents a single product or service entry within an order, containing the specific stock item(s), quantity, pricing, and fulfillment details for that part of the transaction. |
| Listing | A Listing is a sellable product offering in your catalog that defines what customers can purchase or rent. Listings connect to SKUs and stock items to manage availability, pricing, variants, and publishing settings across your sales channels. |
| Location | A location is any physical or logical place that holds inventory and connects to fulfillment operations — whether it's a storefront, warehouse, service center, or fulfillment hub. Locations enable multi-site operations with unified inventory visibility. |
| Note | An internal note on a stock item's timeline — an inspection, a condition remark, a repair log. Notes are added on the stock item's Events tab and do not block availability. |
| Online Store | The Online Store is a whitelabel e-commerce storefront provided by TWICE that enables customers to browse, configure, and purchase or rent products directly. It provides a fully customizable, mobile-responsive shopping experience under your own branding, integrated with your inventory, catalog, and order management systems. |
| Fulfillment | Fulfillment is the process of delivering products to customers, including inventory allocation, pickup/delivery coordination, returns processing, and completing the physical handoff of items. |
| Fulfillment Field | A field shop staff fill in while fulfilling an order, such as a fitting number, a lock code or a meter reading. Defined under Settings → Attributes & tags, attached to a SKU or a stock item, and filled in under Fulfillment details on the order. |
| Order | A customer-facing order that tracks the entire journey from initial reservation through fulfillment, payment, and completion. Orders are manageable under 'Orders' and block inventory availability. They can contain bookings (rentals), sales, subscriptions, and buybacks. |
| Order Lifecycle | The Order Lifecycle describes the complete journey of an order from creation through fulfillment, completion, and post-order processes. Understanding order lifecycle stages helps manage operations, automate workflows, and track performance across different order types and statuses. |
| Order Reference | The customer- and merchant-facing identifier of an Order — the sequence value rendered through your order numbering format (#1042, S-001042). The underlying sequence value itself is the order number; both are allocated when the order leaves pending. |
| Order Types | An order does not carry a type of its own. Every line item has a purchase type — booking, sale, subscription or buyback — and one order can mix them, such as a rented camera alongside a memory card sold outright. Purchase type drives pricing, the fulfillment rules that apply, and which lifecycle transitions are valid. |
| Payment | A Payment is connected to a checkout and produces the VAT receipt. Payments always point to Line Items on the order and can include multiple transactions. A checkout can have multiple payments to support partial payment scenarios. |
| Price Table | A Price Table is a pricing structure that defines how a listing is priced — rental rates by duration, sale prices, and subscription plans — with optional date windows and per-variant overrides. |
| Reservation | An internal reservation blocks a stock item for a period without an order — for maintenance, storage or internal use. Reservations are created on the stock item's Events tab, or by a workflow, and can be open-ended until closed. |
| Sales Channel | A sales channel is where customers can browse and buy from you. Today that is the Online Store, which you enable or disable per location. Orders also record where they came from — the storefront, the admin, or the API. |
| SKU (Stock Keeping Unit) | A SKU (Stock Keeping Unit) is a product-level definition that groups similar stock items. It holds the shared name, code, category, attributes and base purchase price, which linked stock items inherit unless overridden. Selling prices are not on the SKU — they belong to listings and price tables. |
| State | State is the current operational condition of an entity, set automatically by events in the system. Stock items have State (In / Out — whether the item is at hand or with a customer). Orders have Payment State (Paid / Partially Paid / Unpaid) and Fulfillment State (Unfulfilled / Partially fulfilled / Fulfilled / Partially returned / Returned). |
| Status | Status is the lifecycle stage of an entity; values differ per entity type. Stock items are Active, Inactive or Draft. Orders are Pending, Draft, Open, Active or Closed, with Pending the in-flight checkout order. Listings are Public or Draft; archiving is separate. Status is set manually or by workflows, unlike state, which events set for you. |
| Stock Code / Item Code | A stock code (also called an item code) identifies an inventory record. A record can carry several at once — an internal asset tag, a printed barcode, a manufacturer serial — and scanning any of them finds it. Codes are generated for you or entered yourself, and each must be unique across your account. |
| Stock Item | A stock item is a single item in your inventory — the digital twin of a physical thing you own. Stock items are held in inventory records: one record per item when you track them individually, or one record covering several identical items when you do not. How you track them is your choice. |
| Stock Item State | Stock Item State tracks whether a stock item is currently In (at hand in your inventory) or Out (in a customer's possession). State changes automatically based on fulfillment and returns on orders. |
| Stock Item Status | The operational availability of a stock item. Active items count toward availability and can be assigned to orders. Inactive items are excluded from operations — under repair, retired, lost or sold — while their record and history are preserved. Draft means registration is still in progress. For temporary unavailability, use a reservation instead. |
| Transaction | A Transaction is comparable to a payment receipt from a payment terminal. A payment can include multiple transactions—for example, a split payment (lunch voucher + cash = 2 transactions, 1 payment) or a payment with a refund (original charge + refund = 2 transactions, 1 payment). |
| Variant | A Variant is a specific version of a listing along an axis you define — size, colour, frame — each axis with its own values. Customers pick a value per axis, and a variant can carry its own price multiplier or override. Rental periods are not variants; they come from the price table. |
Admin interface terms
These are the admin’s own strings, not documentation concepts. Searching them finds the page that says what to do. Each one is quoted here as the product renders it.| Term in the interface | What it means | Where it appears |
|---|---|---|
| Add Line Item | The dialog where an order line is filled in | An order, when you add a listing or press Create new |
| Change listing | Swaps the line’s listing for another | Top of Add Line Item, on catalog listings only |
| Purchase Type | Booking, sale or subscription | Add Line Item |
| Purchase option | The pricing row the line is priced from. Required; Add stays disabled while it is empty | Add Line Item |
| Purchase option (filter) | Narrows the listing table to bookings or sales. A different field from the one above | Add a listing |
| Purchase options | The card that decides whether a listing offers bookings, sales or both | A listing’s Pricing tab |
| Fulfillment | The section showing what stock fills the line | Add Line Item |
| Fulfilment criteria | The rules a listing picks its stock items by | The Fulfillment section |
| ”No fulfillment rules configured” | The listing is not bound to stock. Availability is unlimited, so you can oversell | The Fulfillment section |
| ”Item is not available” | Nothing matching is free for the chosen dates | Add a listing |
| Track individually | Whether each unit becomes its own record or one record carries a balance. Fixed at creation | Stock item registration |
| Unit price | The line’s price per unit, read from the selected pricing row | Add Line Item |
Related articles
Key Concepts
Dive deep into each concept with full documentation including relationships, lifecycle, and practical usage
Navigating in TWICE
Learn what each view, page, and tab in the TWICE Admin is used for
Updates
Release notes and what’s new in TWICE