Purchasing and receiving

From supplier order to received inventory, one record.

Reordering stock should leave a trail from the supplier decision through every partial delivery. LiftedPOS keeps purchase orders close to the product and inventory records that prompted the buy and the receiving work that closes it.

INSPECTION PATHOpen Purchase Orders, inspect a seeded order and supplier, then compare ordered and received quantities.

LiftedPOS purchase orders with supplier, location, total, expected delivery, and receiving state
Current LiftedPOS operating surface · safe seeded data
  1. 01
    Cost context

    Supplier, destination, item cost, charges, delivery, tracking, and notes stay together.

  2. 02
    Actual receipt

    Ordered, previously received, current, and remaining quantities preserve partial delivery truth.

  3. 03
    Recovery trail

    Actor, time, note, and item receipt history support refresh-before-retry recovery.

Cost context

Supplier, destination, item cost, charges, delivery, tracking, and notes stay together.

Actual receipt

Ordered, previously received, current, and remaining quantities preserve partial delivery truth.

Recovery trail

Actor, time, note, and item receipt history support refresh-before-retry recovery.

01

Build a supplier order with cost and destination context

Create the purchase order against a supplier and location, record ordered quantities and item costs, then keep shipping, tax, and other charges, expected delivery, tracking, notes, subtotal, grand total, and printable order context on the record.

02

Receive what arrived, not what was promised

The operator enters the quantity accepted now. The ordered, previously received, current receipt, and remaining quantities stay visible so a partial delivery can remain on the same purchase order without flattening several deliveries into one number.

03

Use receipt history as the recovery record

Receipt rows preserve actor, time, note, and item quantities. One receiving request refreshes counters, records receipt history, increments inventory, and updates order state together; after an interrupted response, refresh the order before submitting more quantity.

04

Use reorder suggestions as a decision aid

Reorder suggestions use recent location sales and lead-time and buffer assumptions to surface a quantity decision. The operator still selects the supplier and creates, approves, and sends the purchase order; a suggestion is not an automatic supplier transmission.

05

Follow the order through its accountable state

Current orders can move through draft, sent, partially received, received, cancelled, and closed states. Purchase orders share supplier, product, cost, location, inventory, receipt, and status context without claiming case-pack, lot, serial, expiry, or accounting three-way matching.

Receive one supplier order in two deliveries

Build a purchase order with item cost, shipping, tax, another charge, expected delivery, tracking, and notes. Receive only part of one line, refresh, and inspect ordered, prior, current, and remaining quantities plus receipt actor and time. Finish the balance in a second receipt and confirm inventory and order state. Simulate an interrupted response only in a controlled test, then refresh before retrying.

Inspect in the live demo

Open Purchase Orders, inspect a seeded order and supplier, then compare ordered and received quantities. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.

Move from the feature to the operation

This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.

See the capability inside a working store.

Run it with safe demo data, then map the locations, roles, devices, and configuration your operation needs.