fashion boutique pos software in Kenya faces a particular Saturday problem: the black dress in size ten is in a fitting room, the last cream one is promised for pickup, and an online shopper just paid for the same style.
Accurate availability begins at the individual variation.
Give Every Colour and Size Its Own Stock Record
In fashion boutique pos software in Kenya, a style contains many sellable variants.
A dress style is not a single sellable item when it comes in four colours and five sizes. Each stocked combination needs a distinct code and available quantity.
Use a consistent size scale for each brand, but preserve the maker’s label. A UK 12, an EU 40 and an unmarked local medium should not be silently merged.
A fashion boutique pos software in Kenya variation record should show colour, size, cut and brand separately. Staff can then identify the exact piece a customer tried or ordered.
Photograph colour under consistent light and retain a plain-language shade name. “Wine” and “burgundy” may describe the same shipment, but a customer may regard them as different.
Check barcode labels against the garment when receiving a delivery. A supplier sticker on the wrong size creates a systematic error every time the item is scanned.
Keep one code per actual variant even when two colours share a price. The code exists to control fulfilment and returns, not just to print a price tag.
The fashion boutique pos software in Kenya stock view should distinguish the last saleable medium from a stained try-on piece. Both are physically present, but only one can fulfil an online order.
Review zero-quantity variants before hiding them from search. Staff may need their history to handle an exchange or ask the supplier for a restock.
Receive New Collections Without Guessing Sizes
For fashion boutique pos software in Kenya, intake begins with variant counts.
A delivery carton may contain an uneven size run even when the purchase order requested equal quantities. Count each colour and size physically before accepting the supplier’s list.
Compare received pieces with the ordered style codes, fabric composition and agreed finish. A new collection label does not prove the production batch matches the approved sample.
With fashion boutique pos software in Kenya, a partial receipt should increase only the variants actually unpacked. The missing small sizes remain outstanding on the supplier order.
Inspect seams, zips, buttons and care labels during intake. Record defects before the pieces reach display racks or a customer fitting room.
If a designer supplies untagged garments, attach boutique codes without obscuring the maker’s identification. The code must survive handling, returns and stock counts.
Record wholesale cost, delivery date and season for each batch. Those details support later markdown decisions without forcing staff to infer age from where a dress hangs.
The fashion boutique pos software in Kenya receiving history can separate supplier shortages from in-store shrinkage. A missing blouse never unpacked should not be blamed on a cashier.
Put unverified cartons in a receiving area, not directly on the sales floor. A piece becomes available only after its variant, condition and quantity are confirmed.
Manage Fitting Room Holds With Clear Expiry Times
With fashion boutique pos software in Kenya, temporary holds need short deadlines.
The last pair of trousers in a popular size may be behind a fitting-room curtain. A salesperson must not promise immediate pickup to someone calling from another branch.
Use a short fitting-room hold linked to a staff member and customer session. Return unpurchased pieces to available stock promptly after inspection.
A fashion boutique pos software in Kenya hold should be different from a prepaid reservation. An unpaid try-on cannot block a paid order indefinitely.
Check garments for makeup marks, loose stitching and missing accessories after each fitting. A visibly damaged item should move to review rather than straight back to the rail.
Number the items entering and leaving each room during busy hours. A simple token and a count help staff spot missing hangers before customers leave.
If a buyer asks to hold a dress until evening, state the exact expiry and whether a deposit is required. Make the same rule apply across shifts.
The fashion boutique pos software in Kenya availability screen can show a temporary hold with its deadline. That is more honest than either displaying zero stock or promising immediate collection.
At closing, release abandoned fitting-room holds and reconcile the physical rail. A digital hold lingering overnight can make a complete size run appear broken online.
Reserve Pieces Across Store and Online Channels
Through fashion boutique pos software in Kenya, channels share one stock promise.
An online order for the last green blouse should immediately protect that exact size from a counter sale. The boutique needs one shared view of sellable stock.
Define the reservation point: order placement, confirmed payment or manual approval. A cart that has not been checked out should not block scarce pieces for hours.
In fashion boutique pos software in Kenya, display reservations by channel and expiry. Staff can distinguish paid click-and-collect stock from an unconfirmed telephone request.
If the store and website update at different speeds, hold a small safety quantity for popular styles. Disclose any out-of-stock order quickly rather than quietly substituting a colour.
For a multi-item basket, check whether all variants are physically pickable before promising one collection time. A missing size can affect the whole customer’s plan.
Set rules for staff-held items, influencer loan samples and photo-shoot pieces. A garment absent from the rack may still need a named owner and return date.
The fashion boutique pos software in Kenya audit trail should show which sale or reservation consumed the last unit. This helps resolve two customers claiming the same dress.
Release cancelled online holds through a documented status change. Leaving a cancelled order in reserved stock creates an invisible shortage on both channels.
Prepare Click-and-Collect Orders by Exact Variant
In fashion boutique pos software in Kenya, paid does not mean picked.
For online pickup, the packing slip should show the garment code, colour, size and any accessories. A style photograph alone may not distinguish navy from charcoal.
Pick from the correct location and inspect condition before messaging the buyer. A payment confirmation should not trigger a pickup notice while the garment remains on an unknown rail.
A fashion boutique pos software in Kenya collection record should move through paid, picked, ready and collected. Each stage answers a different question from a customer travelling to the shop.
Label the bag with order number and pickup name without exposing unnecessary personal details to everyone in the boutique. Store it away from public shopping stock.
Agree how long a paid order can remain awaiting collection and what happens afterwards. The rule should be visible before purchase, especially for limited collections.
At handover, check the order reference and inspect the garment with the recipient where practical. Note if someone else is authorised to collect on the buyer’s behalf.
The fashion boutique pos software in Kenya record should capture the actual pickup date rather than treating payment date as fulfilment. This distinction matters for exchange windows and disputes.
If the customer wants a different size at pickup, process an exchange against the original order. Do not simply swap bags and leave the stock figures wrong.
Plan Size Runs From Actual Demand
For fashion boutique pos software in Kenya, missed requests inform next orders.
Selling out of mediums tells only part of the story if customers asked for extra-larges that were never stocked. Keep a simple record of missed size requests alongside sales.
Review demand by style and fit, not a single boutique-wide size ratio. A fitted blazer and a loose kaftan may sell to different size distributions.
The fashion boutique pos software in Kenya sales view should distinguish sell-through from initial quantity. Two sales from two units tell a different story from two sales from twenty.
Ask staff to note systematic fitting feedback, such as a brand running small at the waist. That can improve future buying without falsely relabelling the manufacturer’s sizes.
When repeating a design, order additional popular sizes while keeping enough breadth for customers who buy less common ones. Optimisation should not mean abandoning the whole size range.
Measure lost sales during a new collection’s first fortnight. Later requests may reflect customers discovering an empty rail rather than true lack of demand.
A fashion boutique pos software in Kenya reorder report should consider supplier lead time and remaining season. Restocking a short-lived trend after its peak can create markdown losses.
Carry customer-approved special size orders separately from speculative stock. The buyer’s measurements and deposit terms need their own record.
Manage Consignment Pieces From Local Designers
With fashion boutique pos software in Kenya, ownership remains visible after display.
Consigned clothing belongs to the designer until sold under the agreed arrangement. Keep the owner, commission rate, agreed retail price and settlement date per piece.
Receive each garment with a signed condition note and unique code. A designer’s handwritten label may not reliably distinguish two identical-looking skirts in different sizes.
A fashion boutique pos software in Kenya consignment sale should calculate the boutique share and designer amount from the actual selling price. A later markdown must follow the contract.
Agree who authorises discounts, alterations and damage claims before placing items on display. Otherwise a cashier may sell below the designer’s approved minimum price.
Separate consigned stock from owned stock in counts and financial reporting. Physically both hang on the same rail, but the inventory obligations differ.
For unsold pieces, record the return date and condition at handover. A missing belt or makeup mark can become a dispute if no intake record exists.
The fashion boutique pos software in Kenya designer statement should list sold codes, sale dates, discounts, commission and balance due. A round-number payout cannot be audited easily.
Reconcile customer returns before paying final settlements. A returned dress may reverse a sale or require a different arrangement depending on when it came back.
Set Seasonal Markdown Rules Before Sale Day
In fashion boutique pos software in Kenya, discounts need an approved clock.
A holiday collection may move quickly in December and stall in January. Set review dates and sell-through thresholds before staff start improvising discounts at the counter.
Plan markdowns at the individual style or variant level. A sold-out black medium should not force a discount on every remaining size of that design.
With fashion boutique pos software in Kenya, schedule start and end times for approved prices. The till, shelf ticket and online listing should agree during the promotion.
Identify stock excluded from markdowns, especially designer consignment with separate price authority. Tell staff what to do if a customer presents an outdated sale tag.
Calculate margin after discount and any commission. A dramatic percentage-off sign can turn a slow item into a loss once selling costs are included.
For a short sale, use the original tagged price and approved markdown rather than manually overwriting the catalogue price. Historical comparisons need both figures.
The fashion boutique pos software in Kenya sale report should show units cleared and remaining sizes. A promotion that moves only popular sizes may leave the original problem untouched.
Take down expired signage promptly and verify online prices after the end time. A mismatch at checkout can undermine trust and create avoidable refund discussions.
Process Size Exchanges Without Distorting Stock
Through fashion boutique pos software in Kenya, both exchange variants remain visible.
An exchange is not simply a new sale of the replacement dress. It returns one exact variant and issues another, often with a price or condition difference.
Check the original receipt, garment condition, tags and applicable policy. Explain any hygiene or alteration restrictions before accepting the piece back onto saleable stock.
A fashion boutique pos software in Kenya exchange record should link both variants to the original transaction. Staff can then see which size left and which size came back.
If the replacement is more expensive, collect the balance against the same exchange. If cheaper, document the agreed refund or credit treatment clearly.
Inspect returned clothing for perfume, makeup, missing buttons or wear. A garment may be eligible for a remedy but not fit to go directly onto the public rack.
For a faulty seam, treat the customer’s statutory rights separately from a discretionary change-of-mind exchange. A printed “no exchanges” sign does not eliminate defect remedies.
The fashion boutique pos software in Kenya return reason should distinguish fit, colour preference and product defect. Repeated fit exchanges can expose a misleading size chart.
Print or send a document showing the original sale, returned piece, replacement and any payment difference. The customer should not need two unrelated receipts to reconstruct the outcome.
Record Alterations and Tailor Handoffs
For fashion boutique pos software in Kenya, fitting instructions follow the garment.
Pinning a hem at the boutique does not finish an alteration order. Record garment code, measurements, requested changes, promised date and who is responsible for the work.
Photograph the garment’s condition and note any existing marks before it leaves the shop. A signed alteration slip protects both customer and tailor.
A fashion boutique pos software in Kenya alteration job should remain connected to the original sale. A customer collecting later needs one reference for garment, payment and fitting notes.
State whether alteration charges are included or separate and whether the change affects exchange eligibility. The buyer should approve the work before fabric is cut.
Track pieces sent to an external tailor as in transit, not missing stock. Put collection and return dates on a named handover record.
Check workmanship at return, including seams, length and fastening. Do not tell the customer a piece is ready based solely on a tailor’s message.
The fashion boutique pos software in Kenya collection stage should show the final fitting and any correction requested. An incomplete hem remains an open service obligation.
For event wear with a fixed date, agree a buffer for a second fitting. A promised same-day correction can fail when the customer is travelling the next morning.
Count Stock by Variant During Busy Trading
With fashion boutique pos software in Kenya, a style total hides discrepancies.
A total of twelve shirts can hide that two medium creams are missing and two extra-large blacks were mislabelled. Count colour and size combinations, not just style totals.
Schedule short counts for premium items and fast-moving racks without closing the boutique. Assign one person to count while another verifies uncertain variants.
A fashion boutique pos software in Kenya count sheet should show floor, fitting-room, stockroom and pickup-hold locations. Every piece needs a state and place.
Reconcile sales and returns that occurred during the count window. A running till can make a correctly counted rail appear short a moment later.
Investigate wrong-size hangers and swapped tags before writing off stock. Misclassification is often more likely than theft when one variant is short and another has a matching surplus.
Require approval and a reason for adjustments. A damaged, missing or designer-returned piece should not all use the same unexplained shrinkage code.
The fashion boutique pos software in Kenya variance history can expose a repeat problem near one fitting room or delivery handoff. Fix the process before changing another count.
Recheck the most valuable discrepancies physically before posting corrections. A scarf inside a jacket pocket can be found faster than an accounting adjustment can be unwound.
Separate Damaged, Steamed and Photo-Shoot Stock
In fashion boutique pos software in Kenya, off-rail pieces need named locations.
A dress returned with a broken zip is not available to sell even if its barcode still scans. Move it into a condition state with a repair decision.
Steam and inspect new pieces before display, but do not treat preparation as a sale. Track items temporarily off the floor so a colleague can locate them.
In fashion boutique pos software in Kenya, photo-shoot loans should have a named custodian, release date and expected return. They cannot simultaneously fulfil pickup orders.
Check garments after each shoot for makeup, pin holes or lost accessories. Record any discount or repair approval before moving them back to saleable status.
For stained pieces, document whether cleaning is possible and who authorises the expense. Selling an undisclosed defect at full price risks a later complaint.
Keep rejected supplier pieces separate with the original intake record. A claimed return should not reappear on a rail after a routine stockroom tidy.
The fashion boutique pos software in Kenya condition history should show when a repaired item becomes saleable again. A repair note alone does not verify that the result passed inspection.
Label physical bins to match digital states. The system cannot protect a damaged garment if somebody places it back among clean stock.
Handle Payments, Deposits and Store Credit Clearly
For fashion boutique pos software in Kenya, deposits represent unfulfilled commitments.
A customer may pay a deposit to hold a limited dress until payday. State the item, hold expiry, balance and refund conditions on the receipt.
Match M-PESA confirmation to the correct sale, especially when a relative pays. A screenshot should not create a duplicate transaction or release an unpaid garment.
A fashion boutique pos software in Kenya order should distinguish deposit received, garment collected and credit issued. These events affect stock and liabilities in different ways.
If a customer receives store credit after an approved return, give it a traceable value and clear terms. Staff should not manage balances in private notebooks.
For split payments, show cash and mobile money amounts against one receipt. Day-end reconciliation should not count the same dress as two sales.
Confirm discount eligibility before final payment. A staff concession, promotional markdown and consignment designer price each require a different authority.
The fashion boutique pos software in Kenya record can link an online payment to later collection and any exchange. This prevents a refund being processed against the wrong channel.
At closing, compare collected payments, outstanding deposits and garments still on hold. An open balance must have a named customer and a real piece of clothing behind it.
Keep Customer Measurements and Preferences Appropriate
A returning customer may appreciate a note that one brand runs narrow at the shoulder. Record useful fit preferences only with appropriate consent and limited staff access.
Measurements can change, so date them and reconfirm before alterations or special orders. A previous waist size is not a reliable instruction for a new custom fitting.
A fashion boutique pos software in Kenya customer history should help locate a prior garment or exchange, not expose sensitive personal commentary to every cashier.
Avoid recording body judgments in free-text notes. Use factual fit observations such as “requested longer sleeve” and let the customer correct an inaccurate preference.
If staff take fitting photos, explain their purpose and request permission. Keep them only as long as needed under the boutique’s privacy practice.
Separate consent for marketing messages from contact details needed for collection. A buyer collecting a paid dress should not be enrolled in promotions by default.
The fashion boutique pos software in Kenya access model can allow a fitter to view alteration instructions without exposing unnecessary payment history.
Review stale profiles periodically. A discontinued size guide or old event date can mislead staff more than it helps them serve the customer.
Use Sell-Through and Returns to Buy Better
At season end, compare units bought, sold, exchanged, marked down and still held. Gross sales alone can disguise a collection that required heavy discounts.
Review each size and colour rather than declaring the entire style successful. One shade may sell out while another consumes most of the rail space.
A fashion boutique pos software in Kenya buying report should include margin after markdown and designer commission. A busy consignment rack may contribute less than quieter owned pieces.
Count requests for unavailable sizes and reasons for returns. A pattern of tight sleeves may indicate a production issue, not weak demand for the design.
Compare arrival date with first sale and final clearance. Late supplier delivery can shorten the selling window even when customers like the collection.
Use customer feedback about fabric and care without turning isolated remarks into universal conclusions. Look for repeated evidence before changing a whole size run.
The fashion boutique pos software in Kenya report can distinguish online pickup demand from walk-in demand. Buying decisions should reflect where customers actually found each garment.
Give next season’s buyer a concrete size order, budget and review date. Historical data helps only if someone can change the purchase before production closes.
Train Staff for the Weekend Rush
Assign one colleague to fitting rooms and another to online pickup when a new collection launches. Their tasks require different checks, even if both handle the same garments.
Teach staff to search by variant code and physical location before promising a size. A name shared by two collections can make a quick verbal answer unreliable.
The fashion boutique pos software in Kenya shift handover should list unpaid holds, picked orders, alteration deadlines and disputed exchanges. Those exceptions matter more than a generic sales total.
Set clear authority for markdown overrides, refunds and consignment discounts. A temporary weekend employee should not improvise a designer’s commission agreement.
Keep a fitting-room count at each shift change. This prevents a missing piece being blamed on the next colleague after the room has been left unattended.
When connectivity fails, use an approved fallback with unique references and later reconciliation. A handwritten receipt must not result in a second charge when systems recover.
The fashion boutique pos software in Kenya activity record should show who released a reservation and when. That makes a double-sale problem easier to resolve without guessing.
Before closing, compare pickup bags with paid orders and fitting-room rails with active holds. Assign each unmatched item a next action rather than leaving it for Monday.
Test a Full Collection Cycle Before Launch
Receive a sample style in three sizes and two colours, with one supplier shortage. Verify that only the physically accepted variants appear as available online and in store.
Place the last medium on a fitting-room hold, then attempt an online order. Check how long the hold lasts and what a customer sees if payment succeeds.
A fashion boutique pos software in Kenya trial should include pickup, size exchange, defective return and a designer consignment sale. Review the resulting stock and owner balances.
Schedule a markdown and compare the till price, rail label and online price at both start and end. A mistimed promotion can create dozens of avoidable corrections.
Print a collection slip and ask someone unfamiliar with the stockroom to find the garment. If its code and location do not identify one piece, revise the labels.
Count all six variants after the trial, including garments in fitting rooms and pickup bags. Investigate any difference before the new collection goes live.
The fashion boutique pos software in Kenya record should still show what happened to a returned item and a consigned piece after the sale reversal. Neither can disappear into a generic adjustment.
Assign an owner to clear the supplier shortage and confirm the pickup shelf before opening. The first online buyer should not discover an unresolved receiving error at the counter.
Close the Loop on Unsold and End-of-Season Pieces
At the end of a season, separate pieces worth carrying forward from those requiring a final markdown, designer return or approved donation. Decisions belong at the variant level.
Inspect unsold garments for fading, missing accessories and damaged care labels. A piece that never sold may still have changed condition after months on the rail.
A fashion boutique pos software in Kenya ageing view should show arrival date, original cost, markdown history and remaining sizes. Those facts support a decision more reliable than intuition about rack space.
For consigned pieces, follow the agreed return date and price authority. The boutique should not clear a designer’s dress without permission merely to make room for a new collection.
Record the count and condition of items returned to a designer, with a signed handover. That protects both parties when a garment is later found to be missing a belt.
If clearance stock moves to a pop-up stall, record the transfer and selling prices by code. Otherwise the main boutique may report shortages while the pieces are legitimately elsewhere.
The fashion boutique pos software in Kenya final season report should reconcile sold, exchanged, returned and written-off variants. A style total cannot explain why a particular size remains unsold.
Decide what to reorder only after those quantities are reconciled. A missing pickup bag should not become a false signal that a popular size sold out.
