Choose the receipt location
Select the tenant location receiving stock. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goEnterprise POS → Purchases
What you’ll accomplish
Select the tenant location receiving stock. This section documents the supplier form and the one-product goods-receipt workflow exposed in version 1.0.0.
Follow these steps
- Go to Enterprise POS → Purchases and open the workflow that matches “Choose the receipt location”. Confirm the page or record context before making a change.
- Create or select a supplier.
- Select an active location and tracked active product.
- Enter positive quantity and unit cost.
- Optionally enter lot/batch number, expiry date and notes.
- Receive the purchase.
- Check the purchase record, stock movement and latest product cost.
Fields and options to review
- Guide focus: Select the tenant location receiving stock.
- Supplier name, email, phone, tax ID, address and payment terms
- Supplier, location and product
- Quantity and unit cost
- Lot/batch number
- Expiry date
- Receipt notes
- Purchase status and totals
Rules the system enforces
- Supplier name and valid email are required by the live form/model.
- Quantity and cost must be positive/valid.
- The product must be active and stock-tracked.
- One product line is received per submitted form in the supplied UI.
- Receiving updates on-hand stock and the product’s latest unit cost.
- A stock exception can leave a purchase exception status rather than silently hiding failure.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- The purchase register shows the receipt.
- On-hand stock and purchase movement increase.
- The product cost reflects the latest received unit cost.
Safety checks and troubleshooting
- Verify supplier and quantity before commit.
- Use lot/expiry only as supporting receipt values; no full lot-allocation workflow is exposed.
- Investigate exception status before further stock activity.
Stay within the supported module flow
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
