xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Price Lot — entity reference
REFERENCE · Last reviewed

Price Lot — entity reference

A receipt-cost layer (quantity received, quantity sold and unit price per goods receipt line) that is defined in the metadata but not implemented. It has no storage, no app, no menu, no form and no list view. Nothing in receiving, invoicing or costing creates, reads or draws it down. Because nothing stores it, the platform refuses any attempt to read or save a Price Lot, for example through the data API or an import, with the error "Entity type 'PriceLot' not found in model." A document name setting (default series PL) and a Clone action are seeded for it, but neither can take effect. Receipt costing, FIFO and average consumption, stock valuation and cost of goods sold use the Inventory Cost Lot layers built by the perpetual costing engine. You can see them in the Valuation lots and Consumption lots drills of the Inventory Valuation statement.

Fields

FieldLabelTypeRequiredWhat it does
BranchIdBranchLookup → BranchBranch the cost layer would belong to. Not stored: the entity has no storage.
CreatedDateTimeCreated DateDateAndTimeYes
DocumentDateDocument DateDateDate of the receipt the layer would represent. Not stored. Receipt dates for real cost layers come from the inventory ledger.
ExternalIdExternalExternalIdIdentifier from an external system. Not stored.
GoodsReceiptLineIdGoods Receipt LineLookup → GoodsReceiptLineGoods receipt line the layer would come from. Not stored. Goods receipts never create Price Lots.
IdIdGuidYes
InventoryLedgerIdInventory LedgerLookup → InventoryLedgerInventory ledger row the layer would come from. Not stored. Real cost layers link to their ledger row on the Inventory Cost Lot instead.
IsClosedIs ClosedBooleanWould mark the layer as fully sold. Not stored and never set.
ItemIdItemLookup → ItemItem the layer would cost. Not stored.
LabelLabelTextDisplay label. Not stored.
NameNameTextRecord number. A document name setting with series PL is seeded, but no number is ever issued because no Price Lot can be saved.
PartnerAccountIdPartner AccountLookup → AccountCompany (partner account) the layer would belong to. Not stored.
QuantityQuantityDecimalYesQuantity received into the layer. Not stored. For the quantity behind a real cost layer, see Valuation lots on the Inventory Valuation statement.
SKUIdSKULookup → SKUStock keeping unit the layer would cost. Not stored.
SoldQuantitySold QuantityDecimalYesQuantity drawn from the layer by sales. Not stored. Invoices never draw down Price Lots. Issues are costed through consumption rows against Inventory Cost Lots.
StorageLocationIdStorage LocationLookup → StorageLocationStorage location of the received stock. Not stored.
UnitPriceUnit PriceCurrencyYesCost per unit at receipt. Not stored, and never used for costing or pricing.
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
CloneCloneServerAction (Clone)Create a copy of this record