Historical sales

receipt_timestamp is marked as Must have in the RELEX interface definition. This value is carried on the RELEX pos_transactions interface and must remain semantically intact during migration.

Unique receipt number in location for normal sales. In case sales transaction fulfils an open sales order (ecom or B2B), the order number of the sales order

date is marked as Must have in the RELEX interface definition. This value is carried on the RELEX pos_transactions interface and must remain semantically intact during migration.

time is marked as Must have in the RELEX interface definition. This value is carried on the RELEX pos_transactions interface and must remain semantically intact during migration.

Inventory location code (i.e. code for affected store, warehouse, etc.)

Item code (code for finished product or stock keeping unit)

Transaction quantity in base unit of measure (e.g. SKU, stock unit, piece, smallest possible unit). Quantity sign defines the transaction direction as seen by the warehouse, e.g. outgoing sales is sent as negative quantity. See more detailed instructions in Definitions- tab.

Uniquely identifies the row together with the receipt code.

Value as of revenue of the whole transaction in the location's currency (e.g. €, £, $) excluding sales taxes (e.g. VAT). Value should always be positive as transaction quantity determines the direction of the transaction.

Value of the whole transaction including sales taxes (VAT) in the location's currency (e.g. €, £, $). Value should always be positive. (Transaction quantity determines the direction of the transaction.)

Stores the RELEX pos_transactions.tax_amount value used by the interface workbook for downstream planning, validation, and migration load execution.

Rate of the sales tax, VAT, GST, or a similar sales-related tax, eg. 0.20 to denote 20% sales tax.

Stores the RELEX pos_transactions.purchase_price value used by the interface workbook for downstream planning, validation, and migration load execution.

Consumer's loyalty level, if any. Can have values such as: "No", "Basic", "Gold", "Platinum" but these are not tighly restricted

The method in which the sale was fulfilled.

ZIP (postal) code of the region to which a delivery is made.

ZIP (postal) code of the address of a loyalty customer

In case sales row includes a campaign discount, code of the related campaign. Can include multiple campaign codes separated by comma (,).

In case sales row includes a campaign discount, code of the related campaign. Can include multiple campaign codes separated by comma (,). NOTE: This is the transaction campaign code and should only include transaction level campaigns, eg. 10% off on whole purchase if buying more than 50 CAD total!

The list price of the sales row without campaign or other discounts excluding sales tax

The list price of the sales row without campaign or other discounts including sales tax

Promotion/campaign discount %. Values represented as decimals, e.g. 21% would be 0.21.

Promotion/campaign discount amount. NOTE: This is the transaction promotion discount and should only include transaction level discounts, eg. if 10% off on whole purchase if buying more than 50 CAD total.

Non-promotional row discount (%), e.g. markdown or given by sales rep. The reason for the discount can be elaborated in the "Discount reason" field. Values represented as decimals, e.g. 12% would be 0.12.

Stores the RELEX pos_transactions.discount_reason value used by the interface workbook for downstream planning, validation, and migration load execution.

Identifier of the checkout where the sale took place.

Checkout type, e.g. self-service checkout vs cashier staffed checkout vs service desk

B2B trading partner to whom goods are sold NOTE: Trading partner must not be individual consumer (i.e. loyalty code), as interface must not contain personal data that may fall under any privacy regulation

Additional subtype for sales transactions. Default order types for SALE transactions are: - MARKDOWN_SALE: sales with a reduced price and - SPECIAL_SALE: e.g. to separate big one-time sales. In omnichannel used to distinguish between different types of sales * HOME_DELIVERY * STORE_PICKUP * STORE_SALE

Stores the RELEX pos_transactions.row_timestamp value used by the interface workbook for downstream planning, validation, and migration load execution.