> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/introduction/glossary.md). # Glossary ## Glossary This glossary explains the key terms used in the documentation. The definitions are written from the backend user's perspective, so they are intentionally short and practical. ### General terms | Term | Meaning | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Aquila Flex | A system supporting administrative, commercial, warehouse and reporting processes. | | Aquila | Short name for Aquila Flex used where the context is clear. | | Backend | A web application used to configure and handle processes in the system. | | Web application | A system available through an internet browser. | | VPN | A secure connection to the company network that may be required before opening the backend. | | System menu | Menu with the main work areas. In the layout used in this documentation, it is on the left side of the screen, for example `Documents`, `Reports`, `Settlements`, `Administration` and `Application`. | | Screen | A backend view where the user searches data, adds records or performs operations. | | Section | A separated screen area, such as filter, data, document header or edited item. | | Tab | An additional detail area for a record or document, such as Items, Prices, Attributes or Related documents. | | Record | A single system entry, such as a user, product, business partner, document or price list. | | Results table | A list of records displayed after searching data. | | Filter | A screen section used to narrow the result list. | | Dropdown list | A selection field where the user chooses one of the available values. | | Lookup list | A helper window used to find and select a value, such as a product, business partner or location. | | Required field | A field that must be completed before data can be saved. | | System message | Information displayed by the system after an operation or validation error. | | Save | An operation that stores data in the system. | | Confirm | An operation that finalises a document or process; after confirmation, some data may no longer be editable. | | Cancel | An operation that abandons the current action or closes a message without confirming it. | ### Users and permissions | Term | Meaning | | ------------------- | ----------------------------------------------------------------------------------------------------------------- | | User | An account of a person using the system. A user has a login, password, location and assigned permission template. | | Login | A unique identifier used to log in to the backend. | | Password | User credentials required during login. | | User location | A location assigned to the user or selected while working in the system. | | Role | A set of permissions assigned to a user. The role defines which system functions are available. | | Permission template | A predefined permission set that can be assigned to a user or copied to a new role. | | Permission | A single ability to perform an operation or access a system function. | | Login enabled | A setting that defines whether the user can log in to the system. | | Active user | An account marked as active and available for work according to login settings. | | Inactive user | An account that is blocked or disabled from current work. | | Blocking a user | Deactivating a user account. | | Unblocking a user | Restoring an account to active work. | | User activity audit | A record of actions performed by users in the system. | ### Locations and warehouses | Term | Meaning | | ---------------- | ------------------------------------------------------------------------------------------- | | Location | A store, head office or other organisational unit in whose context the user works. | | Location number | Location identifier used in the system. | | Location owner | Entity assigned to a location. | | Location group | A set of locations handled together, for example for promotions, reports or configuration. | | Warehouse | A stock recording unit assigned to a location. A location may have more than one warehouse. | | Source warehouse | The warehouse from which goods come in a document or operation. | | Target warehouse | The warehouse to which goods are moved in a document or operation. | | Stock level | Product quantity available in a warehouse according to system data. | | Minimum stock | The lowest stock level that should be maintained for a product. | | Below minimum | A situation where product stock falls below the defined minimum level. | ### Dictionaries and configuration | Term | Meaning | | ---------------- | ------------------------------------------------------------------------------------------------------------------ | | Dictionary | A list of values used in different modules, such as payment methods, units of measure, concessions and tax tables. | | Country | A dictionary value used in address data. | | Payment method | A payment type used in documents, settlements and reports. | | Unit of measure | A unit used to record a product, such as piece, kilogram or package. | | Unit conversion | Conversion from one unit of measure to another. | | Concession | A label or requirement assigned to a product when sales require additional classification. | | Tax table | A set of tax rates with their validity periods. | | VAT rate | A tax rate assigned to a product, document or document item. | | Document type | Configuration that defines the document kind and handling rules. | | Document process | A defined workflow for a document, such as save, confirm, print or related documents. | | Cash register | A sales point or sales device configured in the system. | ### Products and master data | Term | Meaning | | --------------------------- | --------------------------------------------------------------------------------------------- | | Product records | A collection of products with basic data, prices, codes, attributes and configuration. | | Product | A product record used in sales, orders, price lists, promotions and warehouse documents. | | Product index | A product number assigned by the system or used as a product identifier. | | Product symbol | A code or symbol that helps search for a product. | | Product name | The full product name visible in product records. | | Cash register name | A shortened product name used on a cash register or label. | | PKWiU | Product classification used where required by a process or regulation. | | Product group | An element of the product structure used to organise products. | | Product group tree | A hierarchical structure of categories, groups and subgroups. | | Product activity | Information whether a product is available for work in a selected location. | | Product activation | Enabling a product for a selected location or location group. | | Product deactivation | Disabling a product for a selected location or location group. | | PLU code | A product code most often used for fresh or weighted products. | | Linked product | A product connected with a base product, such as packaging, bundle or set component. | | Weighted product | A product sold by weight. | | Sales block | A setting that prevents a product from being sold at the cash register. | | Price change block | A setting that prevents a product price from being changed at the cash register. | | Cashier-entered price | A setting that allows the cashier to enter a product price during sales. | | Product image | An image assigned to a product card. | | Image import | A bulk operation for loading product images into the system. | | Product attribute | An additional product feature used for description, filtering or configuration. | | Dynamic attribute | An attribute whose number or values can be extended while working with a product. | | Product label | A template or printout connected with a product. | | Product supplier | A business partner from whom the product can be ordered. | | Order parameters | Product settings used during ordering, such as minimum stock, suppliers and order quantities. | | Order quantity | Product quantity suggested or entered for an order. | | Sales velocity | An indicator used to estimate product demand based on sales history. | | Price history | A list of product price changes in a selected period. | | Product receipts and issues | A view of product warehouse movements in a selected period. | ### Business partners | Term | Meaning | | --------------------- | ------------------------------------------------------------------------------------------------- | | Business partner | A customer, supplier, store or other entity used in documents and reports. | | Business partner type | Classification of a business partner, such as customer, supplier or another system-defined group. | | Registered address | The main address of a business partner. | | Delivery address | Address used for deliveries or logistics documents. | | Contact details | Data such as email, phone or contact person. | | Contract | An agreement or record connected with a business partner and used in commercial processes. | ### Prices and price lists | Term | Meaning | | ---------------------- | ----------------------------------------------------------------------------------------------------- | | Price | A value assigned to a product for a specific use, location or period. | | Global price | A centrally set product price used as the base value. | | Local price | A product price valid for a specific location. It may differ from the global price. | | Sales price | The price at which the product is sold. | | Promotional price | A price valid as part of a promotion or temporary price campaign. | | Initial price | A starting product price used for selected price list types. | | Net purchase price | Declared or recorded product purchase price without tax. | | Price list | A set of prices valid according to defined rules, for example in a period or for a selected location. | | Sales price list | A price list defining product sales prices. | | Price list priority | A value that defines the order of applying price lists when more than one price list is valid. | | Price import from file | Loading prices from a file, most often CSV. | | Sales price update | Moving or activating sales price changes in the system. | ### Promotions and loyalty | Term | Meaning | | ------------------------------- | ------------------------------------------------------------------------------------------------------ | | Promotion | A rule for calculating benefits for sales, based on conditions, rewards, priority and validity period. | | Promotion type | A promotional mechanism, such as percentage discount, amount discount or new price. | | Promotion priority | The weight of a promotion that determines its order compared with other promotions. | | Active promotion | A promotion available for calculation in a defined period and scope. | | Validity period | From and To dates that define when a promotion or price list is active. | | Promotion trigger moment | The moment in the sales process when the system calculates a promotion. | | Promotion confirmation mode | A setting that defines whether and how the cashier confirms promotion application. | | Impact on subsequent promotions | A setting that defines whether an applied promotion affects following promotions. | | Promotion level | A part of the promotion definition containing conditions, rewards and possible exclusions. | | Promotion condition | A rule that must be met before a promotion can be applied. | | Promotion reward | A benefit granted after a condition is met, such as discount, new price or transaction discount. | | Excluding condition | A rule that blocks promotion application in selected cases. | | Promotion basket | A set of products used to define promotion conditions or rewards. | | Promotional coupon | A code or mechanism that enables promotion application. | | Loyalty card | A customer identifier used in loyalty processes. | | Loyalty card type | Classification of loyalty cards available in the system. | ### Documents and warehouse operations | Term | Meaning | | ------------------------------- | ----------------------------------------------------------------------------------------------------- | | Document | An operational record, such as order, receipt, issue, invoice or stocktaking document. | | Document header | The main part of a document containing type, number, location, business partner, warehouse and dates. | | Document footer | Additional text information saved on a document. | | Document item | A single product or entry on a document. | | Edited item | A section where the user enters or changes a document item. | | Source document | A document from which data can be copied or a related document can be created. | | Related document | A document connected with another document in a process, such as order, receipt or issue. | | Document status | A document state defining which operations are still possible, such as save, edit, confirm or print. | | Saved document | A document stored in the system that may remain available for further editing. | | Confirmed document | A finally accepted document; usually it can no longer be modified. | | Import document items from file | Adding document items from an external file. | | Supplier order | A document for ordering goods from a supplier. | | Customer order | An order document created for a customer. | | Shipment order | A document or process connected with shipment preparation. | | Goods allocation | Assigning goods to specific locations or needs. | | External receipt | A document for receiving goods from outside, most often from a supplier. | | External receipt correction | A document correcting a previous external receipt. | | Delivery aviso | Delivery notice that may precede goods receipt. | | Opening balance | A document that enters the initial warehouse stock level. | | Receipt from another warehouse | A document for receiving goods transferred from another warehouse. | | Customer return | A document handling receipt of goods returned by a customer. | | External issue | A document for issuing goods outside. | | Internal issue | A document for issuing goods for internal use. | | Return to supplier | A document for issuing goods returned to a supplier. | | Inter-warehouse transfer | Moving goods between warehouses. | | Transfer to another warehouse | A document for transferring goods to another warehouse or location. | | PMI transfer | A transfer type used in system warehouse processes. | | Liquidation protocol | A document confirming goods liquidation. | | Receipt | An operation that increases warehouse stock. | | Issue | An operation that decreases warehouse stock. | | FIFO | A stock issue method where the oldest batches are issued first. | | LIFO | A stock issue method where the newest batches are issued first. | | Weighted average | A stock valuation method based on the average product cost. | ### Invoices, settlements and payments | Term | Meaning | | ------------------------------ | -------------------------------------------------------------------------- | | Invoice for receipt | An invoice issued based on a sales receipt. | | Invoice correction for receipt | A document correcting an invoice issued for a receipt. | | VAT sales invoice | A VAT sales document. | | VAT invoice correction | A document correcting a VAT invoice. | | VAT invoice for issues | An invoice created based on issue documents. | | Store cash desk | A settlements area related to cash register and store operations. | | Fiscal report | A report from a fiscal device or fiscal process. | | Deferred payment | A payment that is not settled immediately at the moment of sale. | | Cashier settlement | A process for checking and closing a cashier's work. | | Payment | Information about payment method and value on a document or in settlement. | ### Stocktaking | Term | Meaning | | ---------------------- | --------------------------------------------------------------- | | Stocktaking | A process of comparing physical stock with system data. | | Partial stocktaking | Stocktaking limited to selected products, groups or warehouses. | | Full stocktaking | Stocktaking covering the full selected warehouse scope. | | Stocktaking surplus | A difference where physical stock is higher than system stock. | | Stocktaking shortage | A difference where physical stock is lower than system stock. | | Stocktaking difference | The difference between system stock and physical stock. | ### Reports and data export | Term | Meaning | | ---------------- | ------------------------------------------------------------------------------------------ | | Report | A data summary with filtering and export options. | | Local report | A report run for a selected location. | | Central report | A report covering head office data or many locations. | | Document report | A report showing documents according to selected criteria. | | Stock report | A report about stock levels, expiry dates or warehouse value. | | Sales report | A report presenting sales by criteria such as period, product, group, cashier or location. | | Promotion report | A report showing promotion results. | | Report export | Downloading report data to a file. | | XLS | Spreadsheet format used for data export. | | CSV | Text format for tabular data used for import or export. | | PDF | Document format most often used for preview, printout or report sharing. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aquiladynamics.com/aquila-store-user-manual/introduction/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.