Network → Network Transfers uses the Arrow Left Right icon. The current screen is a request/status tracker, not a complete inventory-movement workflow: creating, sending, or receiving a network transfer does not change stock-on-hand in this component. The UI moves directly Requested → Sent → Received, does not capture sent or received quantities, and creates a pending at-cost invoice on receipt from the stored quantity_received values. Use separate verified inventory and accounting controls before treating the transfer as reconciled. The exact Harbor & Hearth history capture was rejected because it exposed private businesses, transfer IDs, quantities, dates, statuses, and values.

Before you beginConfirm the organization and participating locations. Network actions may affect more than one storefront.

Step by step

  1. Go to Network → Network Transfers using the Arrow Left Right icon. Confirm the active business and whether it is the intended source, destination, Enterprise HQ, or Agency context before opening or changing a record.
  2. Use All for every permitted status. Active excludes Received and Cancelled. Completed currently includes Received only—not Cancelled—even though cancelled records still exist in All. Read the count shown only on the active tab as the server total for that filter.
  3. Use Search transfers only for a transfer number. The field waits about 400 milliseconds before querying and does not search source business, destination business, location, product, SKU, requester, note, date, or status.
  4. Results load newest first in pages of 50. Choose Load more (<loaded> of <total>) until the intended transfer is present. No network transfers yet can mean the current filter/search returned none, not that no record exists in another permitted scope.
  5. Choose Request Transfer. Recheck Deliver to (your location) every time. The dialog lists active locations belonging to the current tenant; the selected destination state can persist between dialog openings, so never assume the visible prior choice is still appropriate.
  6. In Search network inventory, enter at least two characters from the grouped master product name or master SKU. Results exclude the current tenant, include only source-location rows with recorded stock greater than zero, and show at most 20 matches.
  7. Read each result’s product name, source business, source location, and displayed <n> in stock. The result does not offer a variant selector and the request stores the master product with variant ID null, even when the network product has variants. Do not use this workflow for a variant-sensitive item unless the exact identity and downstream correction process have been approved.
  8. Choose a result once. The same master product/source business/source location combination cannot be added twice. The line shows product name, master SKU, quantity, and remove X; it does not continue to show the source name or available stock after selection, so resolve each line before adding several similar sources.
  9. Enter a whole requested quantity of at least 1. The input clamps values below 1 but does not cap the request to the displayed stock, reserve inventory, or recheck availability at submission. Independently confirm the exact sellable quantity with the source before sending.
  10. Read Items to request, number of source stores, and Est. cost. Unit cost is calculated from the grouped network product’s total value divided by total stock, not necessarily the selected source location’s actual cost. Treat it as an estimate, not an approved intercompany price or financial document.
  11. Add Notes (optional) with an operational reason and safe handling context. Do not include customer details, payment data, credentials, or other information unnecessary for the source and destination teams.
  12. Choose Submit Request once. CentriPOS groups lines by source tenant plus source location and creates one Requested transfer per group, with pricing model at cost and HQ approval not required. The success message reports how many requests were created.
  13. Submission is not transactional across every group or even across a transfer header and its item rows. A later failure can leave earlier transfer requests—or a header without all intended items—already saved. If an error occurs, close the dialog, search by recent transfer number/time, and inspect every created record before retrying.
  14. Open each transfer card. It shows transfer number, status, From and To business names, item count, total requested units, estimated cost, and creation date. The detail shows From/To locations, each product/master SKU, requested quantity, unit cost each, Total cost basis, Notes, request time, and requester.
  15. For the source business, a Requested record offers Decline and Mark as Sent. There is no approval step or confirmation dialog in this UI; although Approved exists in the status model, this screen does not expose an Approve action. Decline writes Cancelled immediately.
  16. Choose Mark as Sent only after the exact physical items and quantities have left the source and a separate source inventory movement/adjustment has been recorded. The action writes status and shipped-by/time but this dialog captures no shipping note, carrier, tracking, quantity sent, or source stock decrement.
  17. For the destination business, a Sent record offers Mark as Received. Inspect the physical shipment first and record shortage, overage, damage, wrong item/variant, and destination stock through the approved operational workflows before choosing it. There is no confirmation dialog or received-quantity field here.
  18. Mark as Received writes Received plus receiver/time and attempts to create a pending network-transfer invoice. The invoice subtotal is calculated from each item’s stored quantity_received multiplied by unit cost; this screen never sets quantity_received. Do not rely on the generated amount until accounting verifies item quantities, cost basis, invoice existence, subtotal, and both businesses.
  19. Enterprise HQ or Agency context can Cancel another source’s Requested transfer; the source itself sees Decline. Platform is treated as HQ by the data hook but not by this component’s HQ-action flag, so do not assume a platform context exposes Cancel here.
  20. Cancelled records do not appear under Completed in the current query. Find them under All, using their transfer number when known. There is no reopen, edit, delete, print, export, attachment, tracking, or exception-resolution action on this screen.
  21. Reconcile the full path outside this status tracker: source stock before/after and movement ledger; physical shipment evidence; destination count and stock movement; exact product/variant identity; requested versus actually sent/received quantities; pending intercompany invoice and approved cost; and both tenant histories. Received status alone is not proof of inventory or accounting reconciliation.

Screen and contract reference

Control or areaWhat it means
Arrow Left Right iconExact CentriPOS navigation and page icon for Network Transfers.
AllEvery permitted transfer status, including Cancelled and Received.
ActiveAny status except Received or Cancelled.
CompletedReceived only in the current query; Cancelled is not included.
Active-tab countExact server count for the selected All, Active, or Completed filter.
Search transfersDebounced transfer-number search only.
Load moreFetches the next page of up to 50 newest-first transfer records.
Request TransferOpens the destination, network-product search, requested items, estimate, and notes dialog.
Deliver to (your location)Active current-tenant destination location; recheck because dialog state can persist.
Search network inventoryRequires two characters; matches master product name/SKU, excludes own-tenant and nonpositive source-location stock, and returns at most 20 rows.
Displayed in stockRecorded source-location stock at search time; not reserved, capped, or revalidated by submission.
Variant boundaryNo variant picker is exposed and request lines store variant ID null.
Requested quantityInteger-like input clamped to at least 1 but not capped to displayed stock.
Duplicate boundarySame master product/source tenant/source location cannot be added twice in one dialog.
Estimated costRequested quantity multiplied by grouped product value-per-unit; not proven source-location cost.
NotesOptional request context shared with the transfer record.
Submit RequestCreates one transfer per source-tenant/source-location group with Requested status.
Partial-create boundaryGrouped transfers and their item inserts occur sequentially without one encompassing transaction.
Transfer cardNumber, status, From/To businesses, item count, requested units, estimated cost, and date.
Transfer detailFrom/To locations, items, master SKUs, requested quantities, unit cost, total cost basis, notes, requester, and time.
RequestedDestination request exists; no inventory is reserved or moved.
ApprovedStatus supported by the model but no Approve action appears in this screen.
DeclineSource-business immediate transition from Requested to Cancelled.
Mark as SentSource-business immediate status write with shipper/time; no quantity, tracking, or inventory mutation.
Mark as ReceivedDestination-business immediate status write with receiver/time and pending-invoice attempt; no received-quantity or inventory mutation.
HQ / Agency CancelCan cancel another source’s Requested record from eligible component context.
CancelledTerminal request status visible under All, not Completed.
ReceivedTerminal tracker status; not proof that stock or accounting reconciled.
Pending invoiceAttempted on receipt at unit cost using stored quantity_received, which this UI never captures.
No exact screenshotThe Harbor & Hearth /network/transfers capture was rejected because it disclosed private network, identifier, quantity, date, status, and cost information.

Expected result

The intended grouped request records exist once with the correct source, destination, master-product identity, requested quantities, and safe notes; status matches the physical handoff; and separate source stock, destination stock, movement-ledger, actually sent/received quantity, cost basis, and pending intercompany invoice evidence are independently reconciled because this screen does not perform those inventory controls.

Troubleshooting

  • Confirm the organization and participating locations before comparing, publishing, or transferring.
  • Keep local and network-level records distinct when reviewing inventory or catalog values.
  • Check whether your network role allows the action shown in the guide.

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.