Inventory → Transfers uses the exact ArrowLeftRight icon. The operational states are Draft, Requested, Sent, Received, and Cancelled; Approved and Shipped can appear on older records. Sending deducts the requested quantity from the source with negative-stock prevention. Receiving defaults each line to the amount sent, posts the counted quantity to the destination, and returns a shortfall to the source. Transfer creation, sending, receiving, continuation, recall, and deletion each use multiple sequential writes rather than one all-or-nothing transaction, so verify source, destination, and movement evidence before retrying after an error.

Before you beginConfirm the location, product, variant, and unit of measure. Inventory actions create an operational audit trail and can affect availability immediately.

Step by step

  1. Go to Inventory → Transfers, identified by the ArrowLeftRight icon. Confirm the active business and your location access. The list is server-filtered and paged; Load more shows how many currently loaded rows are visible out of the total.
  2. Use All, Drafts, Pending Approval, In Transit, or Completed. Filter by access-scoped locations, exact source store, destination store, product/variant/SKU search, and From/Through dates. Clear resets those filters. Expand a row to see active product/variant, SKU, Requested, Sent, and Received quantities without opening it; choose the row or transfer number for full detail.
  3. Read the list carefully: Created is requested_at, Requested By is the creator, From is the inventory source, To is the requesting/destination location, and Products versus Items means distinct active lines versus summed requested units. Recalled lines are excluded from the expanded active-line list.
  4. Choose New Transfer. To begins with the current operating location when available; From begins blank. Choose two different locations, then verify which site will lose stock and which will receive it. Optionally set the expected transfer date, route the request to an eligible source-location manager, and enter notes.
  5. Add the exact product or variant and enter a whole-unit requested quantity. Review displayed source stock, name, variant, and SKU. Import from sale can add selected unfulfilled sale lines for the destination, preserve their fulfillment link, add an Imported from sale note, and auto-save when both locations are valid. It does not complete the fulfillment.
  6. A new valid draft auto-saves after changes. Save Draft explicitly when the request is not ready; Submit Request changes it to Requested. Creation writes the header and then line rows. Editing an existing Draft or Requested transfer updates the header, deletes all old item rows, and inserts replacements; those writes are not atomic, so an error can leave missing or replaced line data. Reopen and inspect every line before continuing.
  7. Print Slip is available after a transfer record exists. It includes transfer identity/status, dates, source/destination, request/sent/received people when present, tracking/notes, and requested/sent/received line quantities. If the browser blocks the print window, allow pop-ups for CentriPOS and retry printing only.
  8. A Draft can be edited or deleted. A Requested transfer can still be edited, cancelled, or sent. Cancel marks the transfer Cancelled without a stock movement. Confirm that no one has begun physical shipment before cancellation; the current cancellation update does not perform a status compare-and-set or inspect its returned error.
  9. At the source, open the exact Requested transfer and choose Send. Review Expected transfer date, optional Tracking number, and Notes, then choose Approve & Send once. The status compare-and-set prevents two senders from both entering the stock loop.
  10. Sending first claims the transfer as Sent, records approver/shipper/timestamps and notes, then processes each active line sequentially: quantity_sent becomes quantity_requested and a transfer-out movement deducts the source with prevent-negative enabled. This is not atomic. If stock is insufficient or a later line fails, the transfer may already say Sent and earlier lines may already be deducted. Stop and reconcile rather than pressing Send again.
  11. At the destination, open a Sent transfer and choose Receive. Older Approved or Shipped records also expose Receive. Actual received date defaults to today; after a recall it defaults to the original received date, and inventory movements use the selected effective date. Use the true physical receipt date.
  12. Every unreceived active line starts Counted at Expected—the sent quantity—not zero. Physically count every line and change Counted to the nonnegative whole number actually present. The input permits an overage above Expected. Review Match, Over, or Short for each line.
  13. Optionally attach each line to one eligible destination fulfillment with the exact same product and variant from up to 100 recent completed/layaway sale lines in pending, sourcing-needed, ordered, or awaiting-receipt status. A fulfillment can be attached to only one transfer line in the dialog. Receipt later marks the linked sale line received and records the source location, but a failed follow-up update is not surfaced by this caller; verify fulfillment separately.
  14. Choose Confirm Receipt. If any Counted amount differs, CentriPOS first opens Discrepancy Detected. Review Expected, Counted, and Diff. A short quantity is returned to source stock. For a short receipt choose Create continuation transfer for remaining or Close as-is and accept short receipt. An overage adds the full counted amount to destination without a source-side offset, so investigate and obtain authorization before accepting an overage.
  15. Choose Receive Anyway only when every discrepancy and remainder choice is correct. Receiving first claims the transfer as Received, then sequentially updates each line, posts counted transfer-in at destination, updates an attached fulfillment, and returns each shortfall to source. A continuation is created last when chosen. These writes are not one transaction and several updates do not check returned errors.
  16. After receipt, verify the Created, Sent, and Received cards and notes; expand/reopen every line; reconcile source deduction, destination addition, any shortfall return, continuation request, linked fulfillment, and source-linked Inventory Movements. A success toast does not prove every follow-up write completed.
  17. A continuation created for a short receipt is a new Requested transfer using the root transfer number plus the next numeric suffix. It contains only the outstanding quantities and preserves matching sale-line links. The original transfer remains Received. Owners can also choose Continue Backorder later when a received transfer still has remaining sent-versus-received units.
  18. Owners and super admins can choose Recall Receipt on a Received transfer. Enter a required reason and select at least one line with received quantity. With no replacement lines, receipt stock is reversed at destination, short-return effects are reversed where applicable, selected line receipt quantities reset, the transfer returns to Sent, and those lines can be received again.
  19. Recall Receipt can also swap selected received lines for replacement products/variants. In that mode, the selected original receipt is removed from destination and restored to source, replacements are inserted as already sent and received, source/destination replacement movements post, and the transfer remains Received. This is a high-impact sequential correction, not a simple label edit; reconcile every movement and the recall-history record.
  20. Delete & Rebalance is owner-level destructive removal for a Received transfer. It sequentially subtracts each nonrecalled received quantity from destination, restores each sent quantity to source, then deletes all item rows and the transfer. Its delete and movement calls are not protected by one transaction and several returned errors are unchecked. Use only after a documented approval and verify that both stock planes and movement evidence balance.
  21. Do not use Delete & Rebalance as an ordinary correction when Recall Receipt can preserve the transfer and its recall audit. Never delete/rebalance, recall, receive, or resend merely because the UI state appears stale. Record transfer ID, status, source/destination, line IDs, quantities, timestamps, and error message before support escalation.
  22. No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth Transfers route remained in a loading state during the extended capture window, so no screenshot was retained or replaced with a different inventory screen.

Screen and contract reference

Control or areaWhat it means
ArrowLeftRight iconExact CentriPOS Inventory navigation and empty-state icon for Transfers.
All / Drafts / Pending Approval / In Transit / CompletedServer-side transfer-state views.
Access-scoped location filterRestricts results to selected visible locations.
Source / destination filtersExact From and To location filters.
Product searchServer-side product, variant, or SKU search after a short debounce.
From / Through datesServer-side transfer date range.
Products / ItemsActive line count versus summed requested units.
DraftOpen transfer; can auto-save, be edited, submitted, printed, or deleted.
RequestedAwaiting source action; can be edited, cancelled, printed, or sent.
SentSource quantities have been deducted and the destination can receive.
ReceivedReceipt has been claimed and counted destination movements processed.
CancelledRequested transfer marked cancelled without stock posting.
Approved / ShippedLegacy states that remain receivable.
Import from saleAdds eligible unfulfilled destination-sale lines and retains sale-line linkage.
Print SlipTransfer handoff with identity, route, people, notes/tracking, and requested/sent/received lines.
Approve & SendCompare-and-set status claim followed by sequential source deductions with negative prevention.
ExpectedQuantity sent or, for legacy/unset sent data, quantity requested.
CountedNonnegative whole-unit physical receipt; initially prefilled to Expected.
FulfillmentOptional exact product/variant destination sale-line attachment.
Match / Over / ShortCounted minus Expected classification.
Actual received dateEffective date used for receipt inventory movements.
Discrepancy DetectedMandatory review when any Counted value differs from Expected.
Shortfall returnExpected minus Counted added back to source.
Create continuation transferNew Requested suffix transfer for remaining short units.
Close as-isReceives current count and closes without a continuation.
Continue BackorderOwner action on an already Received transfer with remaining units.
Recall ReceiptOwner/super-admin line-level reversal or replacement workflow with required reason and recall history.
Delete & RebalanceOwner-level destructive stock reversal followed by transfer deletion.
Multi-write boundaryTransfer operations are sequential and not one all-or-nothing transaction.
No public screenshotRejected real loading-state capture; no substituted or fabricated image.

Expected result

The exact transfer, active lines, source, destination, requested/sent/counted quantities, effective dates, people, notes, tracking, fulfillment links, and status sequence are verified; source deductions, destination receipts, shortfall returns or overages, continuation records, recalls/replacements, and movement evidence reconcile line by line; and a partial multi-write result is investigated before any resend, rereceipt, recall, or deletion.

Troubleshooting

  • Confirm the exact product variant and stock location before posting a quantity change.
  • Use the movement ledger to identify the source workflow instead of correcting history directly.
  • Avoid a manual adjustment when receiving, transfer, count, sale, or return is the correct workflow.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.