Start with Bizman Inventory when you need to know what each branch holds, what is travelling between locations and which differences need investigation. Ask BriskRetail to demonstrate a transfer from request through dispatch to counted receipt. A dashboard showing every branch is useful, but it must be backed by records that explain how the quantities changed.
For a business connecting branch sales to those balances, include Bizman Sales and Inventory in the evaluation. One outlet can be short of an item while another has surplus. Moving that surplus should improve availability without creating a second purchase, an internal retail sale or stock that appears at both locations simultaneously.
This guide uses a hypothetical two-branch exercise covering a missing carton, a return and an interrupted connection. The locations and figures are teaching examples, not a client case study or measured delivery performance.
Commercial disclosure: BriskRetail supplies Bizman solutions and benefits when customers choose its services. Bizman Inventory is our primary recommendation for a scoped branch-control evaluation. We have not tested its transfer approvals, reservation, permissions or synchronisation. Each requirement below must be demonstrated on the proposed configuration.
Research checked: 23 October 2026. Official vendor documentation illustrates particular behaviours to examine. It does not establish equivalent Bizman functionality. This article concerns branches of one business; transfers between separate legal entities require their own accounting and documentation review.
IMAGE 01 — COVER PLACEHOLDER · 1600 × 900 px · 16:9. Original illustration of two shop locations linked through a clearly marked in-transit stock stage. Suggested alt text: “Branch stock remains traceable while goods travel between locations.” No real store photograph or fabricated Bizman interface.
1. Define what each stock number means
A branch's physical stock, quantity available for sale and expected incoming delivery are different measures. Staff should know which one they are looking at before promising an item to a customer or approving a transfer.
For a simple example, branch A physically holds 100 units. Twenty are reserved for existing commitments and five are held for inspection. Its available quantity is 100 − 20 − 5 = 75 units. A further 30 units expected from elsewhere should not be added to that available figure before the agreed receiving process is complete.
Shopify's inventory-state documentation separates on-hand, available, committed, unavailable and incoming quantities. In that model, incoming inventory is not available to sell before receipt. This illustrates why a single “stock” column can hide important distinctions. Source: Shopify inventory states.
Ask the Bizman presenter to define each displayed quantity, its location and its last update. Check whether a reservation is an actual enforced allocation or merely a note. Two staff members seeing the same available balance does not prove the system can prevent both from committing the same units.
Keep product identity and units consistent across branches. A carton code at one branch must not resolve to a piece at another. Record location balances under the same intended product identity, while retaining any batch, variant or packaging details needed for the goods being moved.
2. Separate request, approval, dispatch and receipt
A destination branch requests goods; an authorised person decides what can be released; the source counts and dispatches; the destination counts what actually arrives. These events may be close together, but they are not interchangeable.
| Stage | Evidence to record | Stock question to resolve |
|---|---|---|
| Request | Source, destination, product, unit, quantity and reason | Is the quantity merely requested or already reserved? |
| Approval | Approver, authorised quantity and date | Can other sales consume the allocated stock? |
| Dispatch | Actual quantity, reference, handover and time | Has stock left the source and entered transit? |
| Receipt | Actual count, condition, receiver and time | What becomes available at the destination? |
| Exception | Shortage, damage, excess or wrong item | Where does the unresolved quantity remain visible? |
| Closure | Reconciliation and authorised resolution | Is every dispatched unit accounted for? |
Loyverse's transfer-order documentation distinguishes a draft with no stock change, an in-transit state where source stock has reduced and destination stock is unchanged, and a received state. It identifies transfer orders as part of its subscribed Advanced Inventory functionality. This is an example of state changes to inspect, not a recommendation based on a tested Nigerian deployment. Source: Loyverse transfer orders.
Agree who performs each stage and how corrections are approved. Where a small team cannot fully separate duties, arrange a documented review by someone who was not responsible for both dispatch and receipt. Do not use a shared login as the evidence of who accepted goods.
Give the transfer a stable reference that accompanies the goods and the digital records. A chat message can help coordinate arrival, but it should not be the only place the quantity or handover is recorded.
3. Reconcile a missing carton without inventing stock
Assume a hypothetical product contains 12 pieces per carton. Branch A starts with 20 cartons, or 240 pieces; branch B starts with five cartons, or 60 pieces. A dispatches six cartons, or 72 pieces, to B. No other movements occur during this exercise.
| Stage | A stock, pieces | B stock, pieces | Transit or unresolved, pieces | Accounted total |
|---|---|---|---|---|
| Before dispatch | 240 | 60 | 0 | 300 |
| Six cartons dispatched | 168 | 60 | 72 | 300 |
| B counts five cartons received | 168 | 120 | 12 | 300 |
| Final carton found and received | 168 | 132 | 0 | 300 |
After dispatch, 240 − 72 = 168 pieces remain at A. When B counts only five cartons, it receives 5 × 12 = 60 pieces, bringing its balance to 120. The missing carton remains an unresolved 12-piece quantity. The table's 300-unit accounted total includes that unresolved quantity; it is not proof that all 300 units have been physically located.
Do not enter six cartons as received just to close the transfer. Check dispatch count, vehicle or courier handover, receiving evidence and any split delivery. Record who is investigating and the next review time. Avoid treating a mismatch as proof of theft before checking ordinary errors and incomplete deliveries.
In the illustrated resolution, the final carton is found and received, bringing B to 120 + 12 = 132 pieces. If instead it is confirmed lost, an authorised loss movement would reduce the business's recorded stock to 300 − 12 = 288 pieces. Preserve the reason and approval rather than leaving a permanent “in transit” balance or creating a fictitious receipt.
The precise exception location depends on the system. Ask Bizman Inventory to show how the unresolved quantity is kept visible without being available for sale. A transfer marked complete should not hide an unresolved shortage behind a matching headline total.
IMAGE 02 — MISSING-CARTON DIAGRAM PLACEHOLDER · 1440 × 960 px · 3:2. Original flow showing 72 pieces dispatched, 60 received and 12 unresolved until counted or formally written off. Suggested alt text: “A partial branch receipt keeps the missing carton visible without making it saleable.”
4. Record returns and rejected goods as real movements
Continue the scenario in which all six cartons arrived. B now holds 132 pieces and A holds 168. If B returns one eligible carton to A, dispatching 12 pieces leaves B with 120, A with 168 and 12 in return transit. Receipt at A produces 180 at A + 120 at B = 300 pieces.
Link the return transfer to the original reference where the workflow supports it, and state why it is being returned. The return is not an external customer sale or another supplier purchase. It should not inflate consolidated sales or purchasing reports.
If the carton is damaged, record its condition and hold status. Physical receipt does not automatically mean available stock. The receiving branch must know whether the items can be sold, require inspection or need another approved disposition.
Shopify's transfer documentation distinguishes accepting, rejecting and cancelling quantities. In its workflow, cancellation applies to items never shipped, while rejection is recorded without changing location stock quantities. These differences show why staff must understand a button's effect rather than treating every action as “send it back”. Source: Shopify receiving and managing transfers.
For the proposed Bizman setup, demonstrate partial receipt, rejected damage, a return shipment and a correction. Check the stock consequence of each action. Never use cancellation to restore source availability for goods that physically left unless the correct return or correction process explains where they are.
5. Test an interruption at the receiving branch
A destination may lose connectivity while the source remains online. The central dashboard could then know that goods were dispatched without knowing that they physically arrived. Decide what staff can record, what they can sell and what requires escalation during that gap.
Suppose B counts the six cartons but loses connection before receiving confirmation that its entry was saved. When the connection returns, staff should check the original transfer and receipt reference before submitting again. Repeating the action must not create a second 72-piece receipt.
Use an authorised test environment to interrupt the connection before submission, after submission and before the confirmation appears. Inspect the resulting records at both branches. A message saying “failed” can describe a missing response rather than a definitely failed write; the demonstration should resolve that ambiguity.
Loyverse's offline documentation states that stock levels and negative-stock alerts are not displayed offline, and describes other offline limitations. This is a concrete reminder that offline sales capability does not imply current cross-branch availability. Do not transfer those exact limits to Bizman without testing. Source: Loyverse offline behaviour.
Ask for the proposed Bizman Sales and Inventory policy on pending transfers, local transactions and stale branch balances. If staff use a temporary paper record, define how it is uniquely referenced and reconciled once, with the original retained. Do not let a manual fallback become a second independent stock ledger indefinitely.
Read the cloud, offline and hybrid POS guide for the broader outage evaluation. Power, connectivity and payment confirmation remain separate dependencies.
6. Control branch prices and access deliberately
Central control does not necessarily mean every branch has the same selling price. The business may approve branch-specific offers or delivery-related differences. Document which rules are central, which can vary and who approves the change.
Specify the branch, product, effective time, approved price and promotion end date. Test that the change reaches the intended location, that another branch is unaffected and that a disconnected till follows the agreed rule. Historical receipts should retain the price actually used rather than being rewritten when the master price changes.
Define access by responsibility and location. A branch user may need to request transfers and receive goods without changing another branch's counts. An owner may need consolidated reports, while a cashier may need only local operational information. A report filter is not necessarily an access restriction; test direct searches, exports and record access too.
Loyverse's employee-access documentation describes configurable roles and restricted actions. That provides a useful prompt for testing individual permissions, but role names alone do not prove the branch boundaries your business needs. Source: Loyverse employee access rights.
For Bizman, ask to see a denied action as well as a successful one. Try editing another branch's stock, changing an approved transfer and using a disabled account. Inspect the user, time, original value and reason recorded for permitted corrections.
7. Consolidate without counting internal movements as growth
A combined report should distinguish external sales from internal transfers. Moving stock from A to B changes its location, not the total number of units owned by the business. Likewise, adding destination incoming quantities to source balances without respecting dispatch state can overstate the total.
Ask which states and locations a consolidated stock report includes. Can it separately show available, held and in-transit stock? Are physical counts current at both branches? Does the valuation use a consistent basis? Avoid comparing one branch at selling value and another at cost.
Define a common reporting cut-off and retain each branch's last successful update. A daily report prepared while one branch is still uploading transactions should identify that limitation. Calling it “live” does not establish that every source is current or that all operations committed together.
Review transfer performance using open items as well as completed ones. A falling average completion time may look good if old unresolved shipments were excluded. Track dispatch date, expected receipt, elapsed time, exception owner and outcome so aged transit remains visible.
Use branch-level demand when deciding what to move. A surplus at A may already be reserved or needed for an upcoming promotion. A shortage at B may be a counting error. Check those facts before transferring stock simply to make the dashboard look balanced.
8. Use a two-branch acceptance checklist
Run the following in a controlled demonstration with synthetic records. Record pass, fail or unverified, along with the configuration and supporting references. These are proposed tests, not tests performed on Bizman for this article.
| Test | Evidence required | Failure to resolve |
|---|---|---|
| Request without dispatch | Clear distinction between request and actual movement | Stock disappears before the agreed event |
| Competing sale and transfer | Agreed reservation behaviour at the source | Same units committed twice |
| Six cartons sent, five received | 12 pieces remain visible as unresolved | Full receipt posted without the goods |
| Return one carton | Matching return dispatch/receipt; total conserved | Internal return recorded as new external stock |
| Lost response during receipt | Original reference checked; one receipt only | Duplicate stock on retry |
| Branch-specific price change | Correct branch and effective time | Unintended locations or historic receipts altered |
| Restricted user action | Real access denial and useful audit evidence | Filter-only isolation or shared administrator workaround |
| Consolidated report | Branch, hold and transit totals reconcile | Incoming stock counted twice |
Choose rollout gates based on your operation. An unresolved duplicate-receipt problem is more significant than an inconvenient report layout. Identify which gaps can be handled by a documented temporary process and which must be resolved before branches depend on the system.
Train ordinary receiving staff to repeat the count, exception and recovery steps. A successful demonstration by the installer should become a procedure another shift can follow, including whom to contact when the quantities do not agree.
IMAGE 03 — TRANSFER ACCEPTANCE BOARD PLACEHOLDER · 1440 × 810 px · 16:9. Original board showing transfer reference, dispatched quantity, received quantity, unresolved balance and reviewer. Suggested alt text: “Branch-transfer acceptance checks connect each exception to evidence and an owner.”
9. Scope the branch rollout with BriskRetail
Ask BriskRetail to evaluate Bizman Inventory using your actual branch structure and transfer responsibilities. Bring a list of stores and stock locations, packaging rules, existing transfer documents and the exceptions that consume the most management time.
Where branch sales drive replenishment and availability, include Bizman Sales and Inventory in the same demonstration. Confirm what updates automatically, what remains manual and what staff should do when another branch's information is stale. Agree support responsibility and the evidence needed to close a transfer discrepancy.
Explore Bizman or request a Bizman multi-branch workflow demonstration. Start with two representative branches, reconcile the complete transfer cycle and expand once the required controls have been demonstrated and the staff can operate them.
