Start with Bizman Sales and Inventory when several sales channels are competing for the same goods. Ask BriskRetail to demonstrate how a walk-in sale, a WhatsApp order and an online checkout affect the same product and location. The goal is to make a promise to one customer without accidentally promising those units to another.
A customer message is not yet a stock reservation. A payment screenshot is not payment verification. A courier status saying “failed delivery” does not mean the parcel is back on your shelf. Keeping these events separate is the foundation of an explainable order process.
This guide maps the journey from enquiry to payment, dispatch and return, with a worked reservation example and a connector checklist. It covers both deliberate manual entry and evaluated automation. It does not assume an existing Bizman connection to WhatsApp, Shopify, Paystack or a delivery provider.
Commercial disclosure: BriskRetail supplies Bizman solutions and benefits commercially when customers choose its services. Bizman Sales and Inventory is our primary recommendation for a scoped workflow evaluation. Integrations, reservations and automatic updates must be demonstrated on the configuration being proposed; we have not performed those tests.
Research checked: 23 October 2026. Platform policies and documentation can change. All quantities, order references and NGN figures below are hypothetical, with no claimed customer results or current provider tariffs.
IMAGE 01 — COVER PLACEHOLDER · 1600 × 900 px · 16:9. Original illustration of shop counter, chat order and online cart connected to one product-and-location record. Suggested alt text: “Three sales channels draw from an agreed stock record.” Do not imply a verified Bizman connector or reproduce private customer chats.
1. Choose the record that controls availability
Decide where an order becomes a commitment and which record controls the available quantity. Staff can use several interfaces, but they should not maintain unrelated balances that are reconciled only after customers have paid.
For each sellable variant, retain the same intended identity across channels. A website's “navy M” must map to the correct shop item, not merely a matching product title. Confirm the branch or fulfilment location too: stock at another outlet may not be ready for immediate dispatch from this one.
Shopify's inventory documentation distinguishes stock physically on hand from available, committed, unavailable and incoming quantities. In that model, incoming goods are not available before receipt. That illustrates why a catalogue should not blindly publish the largest number it can find. Source: Shopify inventory states.
Define which quantities the customer sees and how recently they were updated. If updates are periodic, record the refresh interval and the response when a connection is stale. “Real time” is not evidence that two simultaneous orders cannot reserve the same final unit.
For Bizman Sales and Inventory, ask the presenter to show the stock record, channel reference and order reference together. A number that looks correct on three screens is less useful than a transaction trail that explains how it changed.
2. Turn a WhatsApp conversation into one identifiable order
Confirm the exact product, variant, quantity, fulfilment method, price and applicable delivery charge with the customer. Then create or update one order with a stable reference. Repeating the conversation on another staff member's phone should not create another sale.
For a manual workflow, assign responsibility for entering the order and checking availability. Record the source as WhatsApp without making the chat transcript the stock ledger. When the same customer later visits the shop to collect, retrieve the existing order instead of starting a second transaction.
Use a clear handover between shifts. Staff need the order reference, current status, any reservation deadline and the next action. They rarely need an unrestricted copy of every customer's messages, addresses and payment screenshots.
Keep catalogue entries consistent with actual variants and prices. If a price or option is no longer valid, correct the channel information and resolve existing enquiries explicitly. A picture of the right product is not enough if the linked SKU points to another size or pack.
3. Set a reservation rule customers and staff can understand
A reservation should identify the order, item, quantity, location and expiry time. Decide which event starts it, who can extend it and what happens at the deadline. A short unpaid hold and a paid order awaiting dispatch are different commitments.
Shopify's draft-order documentation says that unreserved items remain available, while explicitly reserved items become committed; it allows a reservation expiry date and time. This is a useful distinction to test in any proposed system, rather than assuming that saving an order automatically protects stock. Source: Shopify draft-order reservations.
Consider this hypothetical sequence for one variant at one shop. The opening stock is ten eligible units. Reserved units remain physically present but are excluded from available stock.
| Event | Physical units at shop | Reserved units | Available units |
|---|---|---|---|
| Opening | 10 | 0 | 10 |
| WhatsApp order W-01 reserves 3 | 10 | 3 | 7 |
| Walk-in customer buys and takes 2 | 8 | 3 | 5 |
| Online order O-01 reserves 4 | 8 | 7 | 1 |
| W-01 expires unpaid and releases 3 | 8 | 4 | 4 |
| O-01 is fulfilled and leaves the shop | 4 | 0 | 4 |
Final physical stock is 10 − 2 − 4 = 4 units. Releasing W-01 changes the available quantity, not physical stock. Fulfilling O-01 removes the four physical units and clears its reservation; it must not deduct another four from availability after the reservation has already done that work.
If W-01's payment arrives after the hold has expired, do not silently restore the old reservation. Recheck availability and resolve the late payment under the agreed process. Another customer may already have committed those units. A paid exception needs a named owner, not a fabricated negative-stock fulfilment.
4. Keep payment evidence separate from order progress
Record payment attempts and actual verified receipts against the order. A customer clicking a payment link, sending a debit alert or saying “done” does not establish successful payment to the business.
Paystack's verification documentation distinguishes transaction states and describes confirming a transaction by reference. Its guidance also discusses checking payment details before delivering value. This provides an example of verification evidence; it does not establish a Bizman–Paystack integration. Source: Paystack payment verification.
For a hypothetical NGN 18,000 order, a verified NGN 10,000 receipt leaves NGN 8,000 unpaid unless an authorised credit arrangement applies. Display that difference clearly. Whether a part-payment extends the stock hold is a business decision to agree, not an assumption the cashier should make.
Use the payment reconciliation guide for the daily matching process. Keep refunds linked to the original payment and order. A cancelled order and a completed refund are separate events, and a failed refund still needs follow-up.
If two attempts both succeed, investigate the overpayment before authorising a refund. Check which receipts belong to this order and whether a reversal has already occurred. Avoid treating every repeated notification as another payment or another sale.
5. Follow goods and money through delivery
Record what was packed, what left the shop, who accepted the parcel and the reference used to track it. Shipping status, customer delivery confirmation and provider settlement can arrive at different times. Each should update the appropriate part of the order record.
For cash on delivery, confirm the provider's actual collection and remittance terms before offering the service. Ask about service area, failed-attempt charges, returns, settlement schedule and claims. This guide does not assume a provider offers COD in every Nigerian location or promises a particular remittance time.
| Event | Stock consequence to record | Money or follow-up consequence |
|---|---|---|
| Order packed but still at shop | Remains physically present and committed | Payment/COD agreement remains identifiable |
| Parcel handed to courier | Moves to the agreed dispatched or delivery state | Retain handover and tracking evidence |
| Delivery fails | Goods remain outside saleable shop stock | Assign retry/return decision and any agreed charges |
| Parcel physically returned | Count and inspect contents | Resolve refund, fee or customer balance separately |
| Returned goods accepted as saleable | Release only the accepted quantity | Retain return and approval references |
| COD collected but not remitted | No new stock movement | Track money due from provider against settlement evidence |
Suppose a three-unit parcel is refused and is travelling back. Available shelf stock should not increase by three merely because delivery failed. When it arrives, staff find two saleable units and one damaged unit. Record two available and one held or damaged; all three physical units must be accounted for.
For a separate hypothetical COD reconciliation, a provider collects NGN 25,000 and remits NGN 23,500 after an agreed NGN 1,500 deduction. 23,500 + 1,500 = 25,000 explains the collection only if the deduction is supported by the agreement and settlement record. Those figures are invented; they are not a provider tariff or a tax treatment instruction.
IMAGE 02 — ORDER-TO-CASH MAP PLACEHOLDER · 1440 × 960 px · 3:2. Original diagram with separate order, stock, payment and delivery states, including late payment and failed delivery. Suggested alt text: “Payment, delivery and physical stock are reconciled separately against one order.”
6. Distinguish manual entry, official APIs and unofficial automation
A manual WhatsApp workflow can be deliberate: a staff member confirms the enquiry and records the order in the agreed system. An official integration uses the platform's supported interfaces and account permissions. A browser or phone automation that imitates user actions is a different arrangement and should not be sold as an official API connection without evidence.
WhatsApp's developer hub directs businesses to its Business Platform, API references, webhooks and integration resources. That confirms an official development route exists; it does not confirm a ready-made Bizman connector, your account's eligibility or support for every commerce feature. Source: WhatsApp developer hub.
The WhatsApp Business Messaging Policy, updated 23 September 2026, sets conditions on business messaging and commerce features. For the Business Platform, it describes a 24-hour customer-service window and approved templates outside that window. It also requires respecting messaging choices and applies commerce restrictions. Check the applicable rules for the account, messages and products you intend to use. Source: WhatsApp Business Messaging Policy.
Do not assume that an order enquiry is permission for unrelated promotional broadcasts. Give staff a clear boundary between order updates and marketing. Keep customer details restricted to the people and service providers who need them for the agreed process, with appropriate privacy arrangements.
Ask any integration supplier to name the platform, supported connection method, account owner and required permissions. Keep ownership of the business number and commercial accounts clear. Treat pricing, message templates and account restrictions as items to verify in the proposal rather than details to discover after rollout.
7. Evaluate the connector's failure behaviour
A connection is more than a successful first order. It must explain duplicates, delayed updates, changed orders, cancelled holds and failures. Ask who monitors the exceptions and how staff know an update has not reached another channel.
Shopify's developer documentation explains that webhook notifications can be delivered more than once and recommends processing them so duplicates do not create repeated effects. It also describes verifying that a notification came from Shopify. For a retailer, the practical test is simple: replaying one order notification should not create another sale or deduct stock again. Source: Shopify webhook verification.
| Evaluation question | Evidence to request | Gap to record |
|---|---|---|
| What connects to what? | Named platform, account and supported API/app | “WhatsApp integration” without a defined mechanism |
| Which item is updated? | Exact variant, location and channel mapping | Product-name matching that confuses variants |
| When is stock committed? | Demonstrated reservation and competing-order behaviour | Display refresh mistaken for protected allocation |
| What happens on retry? | Same event processed once with a traceable reference | Duplicate orders, payments or deductions |
| How are failures recovered? | Visible queue, owner and reconciliation procedure | Silent missed updates or blind re-entry |
| How do changes flow? | Cancellation, return and late-payment tests | Only new-order creation demonstrated |
| Who owns support and exit? | Responsibilities, export and access-removal process | Dependence on an unnamed personal account |
Request a test where two channels try to buy the final unit. Record which order succeeds, what the other customer sees and whether any payment needs resolution. If the proposed arrangement cannot enforce shared allocation, document the limitation and an operational control rather than promising that overselling is impossible.
Also test a delayed cancellation arriving after dispatch. The system must not make dispatched goods available because it processes an old event without checking the current order state. Ask the supplier to show the final record and explain how contradictory updates are reviewed.
8. Reconcile the channels at the end of the day
Review open reservations, paid-but-unfulfilled orders, late payments, unallocated receipts, delivery exceptions and returned goods awaiting inspection. Keep these as separate queues with an owner and next action. One combined “pending” number is difficult to manage.
Match each completed sale to its channel and order reference without counting it twice. A WhatsApp order collected at the till remains one sale. A courier remittance is settlement of previously collected money, not another sale. A refund does not automatically prove that the goods returned.
Check a sample of variant balances against the physical shelf and active commitments. Investigate mismatches at the event level: was a hold released, a sale duplicated, a parcel marked returned prematurely or a channel mapped to the wrong item? An unexplained stock adjustment may conceal the same fault until the next trading day.
Review stale catalogue information too. If an integration has stopped, decide whether to pause affected offers or require availability confirmation. Give staff an agreed temporary procedure and reconcile its entries once service resumes. Do not keep several emergency spreadsheets running as independent sources of stock truth.
IMAGE 03 — DAILY EXCEPTION REVIEW PLACEHOLDER · 1440 × 810 px · 16:9. Original board showing expired holds, late payments, failed deliveries and unmatched settlements with owners and references. Suggested alt text: “A daily review resolves exceptions across sales channels without duplicating orders.”
9. Demonstrate the complete workflow with BriskRetail
Ask BriskRetail to evaluate Bizman Sales and Inventory against your actual channel mix. Bring your product identifiers, order-entry process, payment providers, delivery arrangements and the rules you want for holds and returns. Start with a representative variant and synthetic transactions.
Run the ten-unit reservation scenario, a payment after expiry, a duplicated notification and a failed delivery with a damaged return. Confirm which steps are manual, which are supported automatically and which require additional integration work. Record pass, fail or unverified with the evidence and responsible supplier.
Agree the customer messages, operational ownership and recovery procedure before expanding. A modest workflow your team can reconcile is a useful foundation for adding channels; unsupported automation claims make that decision harder.
Explore Bizman or request a sales-and-inventory workflow assessment. Ask for the proposed connection scope and demonstrated limitations in writing before committing to an implementation.
