Start with Bizman Sales and Inventory when your stock total looks right but staff cannot find the size, colour or shade a customer wants. Ask BriskRetail to demonstrate the individual item being received, sold, returned and counted. A record saying “12 dresses” is not enough when the question is whether one particular dress is available in navy, size M.
The same issue appears in a beauty shop. Two products can share a brand and range while differing in shade, volume or pack size. Recording them under one convenient name can hide shortages, create wrong-item sales and make replenishment unreliable.
This guide gives you a sample product-and-variant preparation sheet, a bundle calculation and a stock-age review. The boutique and beauty-store examples are hypothetical; they do not describe BriskRetail clients.
Commercial disclosure: BriskRetail supplies Bizman solutions and benefits when customers choose its services. Bizman Sales and Inventory is our primary recommendation for a scoped evaluation of these workflows. We have not tested the proposed variant, bundle, import or return behaviours. Ask for evidence on your proposed configuration before treating them as included capabilities.
Research checked: 23 October 2026. Official vendor documentation illustrates specific behaviours to investigate, not a tested comparison or a claim that another product works identically to Bizman. No current software price or customer saving is assumed.
IMAGE 01 — COVER PLACEHOLDER · 1600 × 900 px · 16:9. Original illustration of a clothing rail and beauty shelf with separate size, colour and shade labels. Suggested alt text: “Distinct clothing variants and beauty shades have their own stock identities.” No customer photograph or fabricated software interface.
1. Separate the product family from the item you sell
A parent product groups related items for browsing and reporting. A sellable variant identifies the exact option whose stock changes. For example, “Everyday dress” is a family; “Everyday dress, navy, M” is one variant. The family total is useful, but it cannot answer an availability question about a specific option.
Odoo's version 19 documentation describes variants with individual inventory and sales records, while the product template can show their combined quantity. It also associates barcodes with variants. That distinction is a useful requirement to put in a Bizman Sales and Inventory demonstration. Source: Odoo product-variant documentation.
For a hypothetical range with three colours and four sizes, there are 3 × 4 = 12 possible combinations. Create only the combinations you actually offer. If a supplier does not make the red XL option, it should not appear as an ordinary item waiting to be reordered.
For beauty products, define the meaningful attributes before creating records: range, shade, finish, volume or other distinguishing presentation. Do not automatically merge products because their packaging looks similar. A 50 ml item and a 100 ml item are separate selling presentations; one is not simply two units of the other unless the actual commercial arrangement and stock model justify that relationship.
2. Give each sellable item a stable identity
Use an internal SKU that uniquely identifies the variant. Keep the same variant identity across branches and record location balances separately. Creating a different product every time it reaches another outlet makes transfers and consolidated reporting harder to reconcile.
Shopify's SKU guidance recommends unique SKUs for products and variants and warns that duplicates can disrupt inventory tracking and integrations. Its multi-location guidance uses the same SKU for the same variant across locations. These are useful data-design examples, not evidence of a particular Bizman integration. Source: Shopify SKU guidance.
Distinguish your internal SKU from a supplier code and a GS1 identifier. A barcode is a way to encode data; the number it carries still needs to identify the intended record. GS1 explains that trade-item references distinguish variations such as model, colour, size and fragrance, and that the complete GTIN must be looked up rather than decoded for product meaning. Source: GS1 trade-item identification.
Retain legitimate supplier identifiers where appropriate and map them deliberately. Do not invent a GS1 number or reuse one product's barcode for several shades just because staff can remember the difference. If internal labels are needed, agree a scheme supported by the proposed system and test for collisions with existing codes.
Store identifiers as text when preparing data. Leading zeroes must survive the journey from supplier sheet to stock record to scanner. Keep discontinued SKUs traceable rather than reassigning them to a new item with a similar name.
3. Prepare a small variant sheet before importing the catalogue
Start with a representative sample and physically count it. The following is a preparation worksheet, not a ready-to-upload Bizman file. The SKU examples are internal teaching codes, not assigned GTINs. “Verify” means obtain the actual identifier; it must not be imported literally as a barcode.
| Parent / variant SKU | Attributes | Selling unit | Opening units at A | Barcode action |
|---|---|---|---|---|
| Everyday dress / ED-NV-S | Navy, S | Piece | 3 | Verify exact variant code |
| Everyday dress / ED-NV-M | Navy, M | Piece | 5 | Verify exact variant code |
| Everyday dress / ED-RD-M | Red, M | Piece | 2 | Verify exact variant code |
| Colour range / CR-04-30 | Shade 04, 30 ml | Sealed unit | 6 | Verify exact shade/volume code |
| Colour range / CR-06-30 | Shade 06, 30 ml | Sealed unit | 4 | Verify exact shade/volume code |
Add supplier reference, cost basis, selling price, active status and location to the actual preparation file. Keep opening quantities separate from purchase history unless the agreed importer explicitly supports both. Otherwise, importing a receipt and the same opening balance can count one delivery twice.
For this sample, the clothing total is 3 + 5 + 2 = 10 pieces, but only five are navy M. The beauty total is ten sealed units, split six and four between two shades. Do not combine these into a business total and lose the item-level checks needed to accept the import.
Ask which field matches existing records and whether a second import creates duplicates, updates selected fields or replaces a whole record. Shopify documents that included blank fields can clear data during an overwrite import and that option changes can recreate variant IDs. That is a warning to test import semantics, not a claim that Bizman's importer behaves the same way. Source: Shopify CSV documentation.
Back up the existing catalogue, rehearse the sample and compare identities, counts and prices before expanding. A file accepted without errors is not proof that it changed the intended records.
4. Keep purchase packs and selling units consistent
Suppose a hypothetical beauty supplier delivers two cases containing 12 sealed units each. If the shop sells individual sealed units, receiving should add 2 × 12 = 24 units, with the cost expressed on a consistent basis. A case costing NGN 18,000 has an illustrative unit cost of 18,000 ÷ 12 = NGN 1,500, before any additional landed-cost adjustments.
A mixed case needs more detail. If it contains six units of shade 04 and six of shade 06, receiving “12 units of the range” does not establish the correct shade balances. Capture the contents against their actual variants and reconcile the sum to the delivery.
In a boutique, an assorted size pack raises the same issue. A supplier's pack may contain one S, two M and one L. Receiving three packs should create three S, six M and three L, not twelve unspecified garments or four of each size.
For Bizman Sales and Inventory, test the purchase unit, conversion and resulting variant balances together. Keep supplier substitutions and shortages visible rather than forcing the delivery to match the order. Unit conversion is not permission to decant, repackage or relabel a cosmetic product; those activities are outside this guide.
5. Make bundles consume the right components
A promotion can combine items without creating extra physical stock. First decide whether the bundle is assembled at sale or is a prepacked item with its own recorded assembly movement. Mixing these approaches can make the same components appear available twice.
Consider a hypothetical gift bundle containing two sealed units of product A, one sealed unit of product B and one pouch. Eligible available quantities already exclude reserved, damaged and held stock.
| Component | Available units | Units per bundle | Complete bundles supported |
|---|---|---|---|
| Product A | 19 | 2 | 9 |
| Product B | 12 | 1 | 12 |
| Pouch | 8 | 1 | 8 |
| Bundle availability | 8 |
The bundle limit is min(floor(19 ÷ 2), 12, 8) = 8. Selling three bundles should consume six A, three B and three pouches, leaving 13 A, 9 B and 5 pouches. The remaining bundle capacity is five.
Shopify documents component-based bundle availability using required quantities and the lowest rounded-down component capacity. It also notes that inventory-tracking and overselling settings affect which components constrain availability. Use the formula as a demonstration case and verify the actual rules in your proposed configuration. Source: Shopify bundle inventory documentation.
Now sell one A separately and check that bundle availability is recalculated from the same component stock. A bundle record with its own unrelated quantity will not protect you from promising components already sold individually.
For a prepacked bundle, demonstrate assembly: remove the components from their available balances and add the finished bundle. Disassembly should reverse the appropriate movement under a controlled process. Do not deduct components again at the final sale if they were already consumed during assembly.
IMAGE 02 — BUNDLE CALCULATION PLACEHOLDER · 1440 × 960 px · 3:2. Original diagram showing two A plus one B plus one pouch, with the pouch limiting availability to eight bundles. Suggested alt text: “Bundle capacity depends on the available quantity of every required component.”
6. Record returns by variant and condition
A returned navy M dress must not increase red M stock merely because both share a price. Find the original transaction, identify the exact variant and record its condition before deciding whether it becomes available again.
For an exchange, keep the returned item and outgoing replacement explicit. Returning one navy M and supplying one navy L changes two variant balances even when no money changes hands. If there is a price difference, the payment adjustment must agree with the exchange record.
Beauty returns require a clear condition-assessment policy. Do not assume that a refunded item is automatically suitable to resell. Record held, damaged or otherwise unavailable stock separately and follow the shop's applicable product-handling rules. This article does not determine whether a particular opened product can be resold.
For bundles, ask how the original price is allocated and what happens when only one component is returned. Agree the financial treatment and physical stock treatment separately. Restocking an entire bundle after receiving one component creates inventory that does not exist.
Test the proposed Bizman workflow with an ordinary return, an exchange and a partial bundle return. Check the sale reference, variant identity, approval and final balances. These are evaluation requirements, not claims that the features have already been tested.
7. Review slow movers at variant level
A style can sell well overall while one size or colour barely moves. Review the exact variants before replenishing the whole range. The same applies to beauty shades: a popular product family does not mean every shade deserves the same order quantity.
The following is a hypothetical 28-day review. Unit costs and quantities are teaching inputs. Age is the age of the oldest remaining receipt, not a claim that every unit was received on that date.
| Variant | Saleable on hand | Units sold in 28 days | Oldest remaining receipt age | Unit cost | Stock at cost |
|---|---|---|---|---|---|
| ED-NV-M | 5 | 20 | 18 days | NGN 8,000 | NGN 40,000 |
| ED-RD-M | 12 | 2 | 96 days | NGN 8,000 | NGN 96,000 |
| CR-06-30 | 9 | 0 | 70 days | NGN 3,000 | NGN 27,000 |
The three lines hold 40,000 + 96,000 + 27,000 = NGN 163,000 at the assumed cost basis. That is capital tied up, not a proven loss. The red dress deserves a different purchasing conversation from the navy dress, despite belonging to the same family.
For the navy variant, five units at a recent rate of 20 per 28 days imply about 5 ÷ (20 ÷ 28) = 7 days of cover if demand continues. For the zero-sales shade, do not divide by zero or invent a useful cover estimate. Investigate visibility, price, product identity, availability history and whether customers actually request it.
Use age bands appropriate to your range and season. A damaged item, an item held for a customer and a saleable slow mover need different actions. Check promotions, stockouts and new receipts before interpreting averages. Transfers or a small tested offer may help, but a discount should follow a margin and eligibility review rather than a blanket rule.
8. Keep reservations and sales channels tied to the same item
A customer asking on WhatsApp for navy M is asking about the same physical variant a walk-in customer may buy. Define when a hold starts, how long it lasts, who can release it and whether payment is required under your policy. A conversation alone should not silently change stock.
Ask the presenter to distinguish on-hand, reserved and available quantities. If five units are physically present and two are validly reserved, the available quantity is three under that simple policy. Cancelling one reservation should restore one available unit without creating a purchase or reversing an unrelated sale.
Do not assume an integration exists because a product can be described as omnichannel. Demonstrate how the proposed channels map to variant IDs, how updates reach each channel and what happens when connectivity fails. A mismatched shade code or stale reservation can cause overselling even when the family total appears sensible.
For a shop using manual order entry, agree a single recording point and a review routine. Assign someone to resolve abandoned holds and incomplete payments. Keep future channel integrations separate from the functionality actually included in your quote.
IMAGE 03 — VARIANT REVIEW BOARD PLACEHOLDER · 1440 × 810 px · 16:9. Original visual showing variant, available stock, reservations, age and next action. Suggested alt text: “A variant review separates stock available to sell from reserved and slow-moving items.”
9. Demonstrate the full cycle before rollout
Ask BriskRetail to demonstrate Bizman Sales and Inventory with a small, representative set of your variants. Include a clothing style with several sizes and colours, two beauty shades, a mixed delivery and one bundle. Use synthetic quantities and transactions until the setup has been checked.
Receive the stock, scan the exact variant, sell a bundle, sell a component separately, exchange a size and record a held return. Then compare the physical test quantities with the item-level report. Inspect an export to confirm that identifiers, units and variant attributes survive outside the application.
Ask which workflows are included, need configuration or remain manual. Record gaps and responsibilities before importing the full catalogue. A reusable demonstration script makes the buying decision clearer than a long list of features with no evidence.
Explore Bizman or request a Bizman Sales and Inventory demonstration. Bring your supplier sheets, labels, bundle rules and return scenarios so the proposal reflects the way your shop actually trades.
