# FIHRIST: full content > FIHRIST is a sales operating system that connects customer conversations (WhatsApp, Messenger, Instagram, email, web chat) with products, orders, and inventory. A customer assistant can answer from store data when enabled, and a sales-analysis assistant helps read performance. Available in Arabic and English. Website: https://fihrist.world/en --- # Turn WhatsApp chats into organized sales. Source: https://fihrist.world/en/solutions/whatsapp-sales-system > Most stores sell on WhatsApp, but orders get lost between messages. FIHRIST links each chat to the customer, product, and order, so your team knows what was asked and what is left. ## What you get - **Every message tied to an order**: Record the order from inside the conversation and come back to it later instead of scrolling through old messages. - **One customer record**: Your team sees who the customer is and what they ordered before replying. - **An owner and a next step**: Assign who follows the conversation and set a reminder so the customer does not go cold. - **Product and price questions**: Show the recorded price, availability, and options while you answer the customer. ## Frequently asked questions ### Does FIHRIST work with WhatsApp? Yes. WhatsApp is a supported channel, alongside Messenger, Instagram, email, and web chat. ### Do I need a WhatsApp Business account? The connection uses the official WhatsApp Business interface, which requires setup on the WhatsApp side. Contact us for the steps that fit your store. ### Does AI reply to customers? When the customer assistant is enabled, it answers questions using store data, and your team can step in at any time. ### Can several team members handle chats? Yes. Each conversation can be assigned to a team member and tracked. --- # Know what sold and what is left in stock. Source: https://fihrist.world/en/solutions/inventory-management-system > When stock is separate from sales, counting becomes guesswork. In FIHRIST the quantity sold from each option is recorded, so remaining stock updates with every sale. ## What you get - **Product options**: Record sizes, colors, and options as separate stock units, each with its own price and quantity. - **QR code per item**: A QR code identifies the item and ties it to sale recording and stock movement, with team permissions. - **From order to quantity**: Each order deducts the quantity sold, so you see what is left without repeated manual counts. - **Product movement**: Compare item movement across periods to see what sells and what stalls. ## Frequently asked questions ### Does FIHRIST link inventory to orders? Yes. The quantity sold is recorded with the order and the remaining stock is shown. ### Does it support barcodes or QR codes? It supports QR codes to identify items and record sales. Contact us for the code types supported in your case. ### Can I set team permissions? Yes. You can set what each member can see or do. ### Do I need separate inventory software? No. Products, orders, and stock live on the same platform, so there is no data to move between tools. --- # An assistant that works from your store data. Source: https://fihrist.world/en/solutions/ai-sales-assistant > Both assistants work from the data recorded in your store, not guesses. One answers customers when enabled, the other helps you read performance. ## What you get - **Customer assistant**: Answers price, availability, and option questions from the products you recorded. - **Sales-analysis assistant**: Compares periods, product movement, and channel results, and explains only what the data supports. - **Review and step-in**: Your team can follow any conversation and step in when a case needs a decision. - **Data is the source of numbers**: The assistant does not assert a cause the data does not support. ## Frequently asked questions ### Does the AI answer automatically? Only when the customer assistant is enabled. You can keep it off and follow up manually. ### What does it base its answers on? On the store data recorded in FIHRIST, such as products, prices, and availability. ### Can it be wrong? Any AI system can make mistakes, which is why your team reviews conversations and steps in when needed. ### Does it support Arabic? Yes. The site and platform work in Arabic and English. --- # All customer channels in one inbox. Source: https://fihrist.world/en/solutions/unified-inbox > Switching between apps slows replies and loses context. FIHRIST brings the five channels into one place and shows who the customer is and what they asked with every message. ## What you get - **Five channels**: WhatsApp, Messenger, Instagram, email, and web chat in a single list. - **Context beside the message**: The customer record and related products and orders are in front of the agent before replying. - **Ownership and status**: Each conversation has an owner and a status, so none is left without follow-up. - **Follow-up reminders**: Set a reminder or follow-up rule so you do not miss a sale. ## Frequently asked questions ### Which channels are supported? WhatsApp, Messenger, Instagram, email, and web chat. ### Does the whole team see every chat? Permissions can be set to control what each member sees. ### Does it keep the customer record? Yes. Conversations are linked to the customer record, products, and orders. ### How long does setup take? It depends on the channels you connect. Contact us for a setup plan that fits your store. --- # A cashier your stock keeps up with. Source: https://fihrist.world/en/solutions/pos-cashier-system > Record a sale in store or from a chat, and the quantity sold moves to stock while the order appears on the customer record. ## What you get - **Fast checkout**: Pick the item and quantity and record the sale in a few steps. - **Stock stays current**: The quantity sold is deducted from the specific option so you know what remains. - **Linked to the customer**: The sale appears on the customer record and supports later follow-up. - **Team permissions**: Decide who can record or edit a sale. ## Frequently asked questions ### Is the cashier part of the platform? Yes. It runs inside FIHRIST on the same products and stock. ### Does it work on mobile? The interface runs in the browser. Contact us to learn which devices suit your store. ### Does it tie the sale to the conversation? Yes. The order can be linked to the conversation it started from. ### Does it support several branches? Contact us to discuss multi-branch needs. --- # One customer record instead of scattered files. Source: https://fihrist.world/en/solutions/sales-crm-for-stores > When customer data is split across WhatsApp, spreadsheets, and a notebook, context is lost. FIHRIST gathers it into one reviewable record. ## What you get - **Customer history**: Conversations, orders, and products on a single page. - **Owner and next step**: Each customer has an owner and a clear follow-up date. - **Group by activity**: See who bought and who went quiet so you can decide whom to follow up. - **Your store data only**: Each store's data is isolated from every other store. ## Frequently asked questions ### How is it different from a spreadsheet? Conversations are linked to the customer and order automatically, so there is no copy and paste between tools. ### Can I import my customers? Contact us to learn how to bring your existing data over. ### Is my data safe? See the security page to learn how permissions and activity records are organized. ### Does it suit small stores? Yes. Start with conversations and orders and expand when you need to. --- # From a customer message to a recorded order. Source: https://fihrist.world/en/solutions/order-management-system > Orders written in messages are easy to forget. In FIHRIST the order starts in the conversation and stays linked to it, the customer, and stock. ## What you get - **Order from the chat**: Create the order while talking to the customer, without leaving the conversation. - **Product, option, and quantity**: Record the product, option, and quantity precisely for each order. - **Effect on stock**: The quantity sold moves to stock so numbers stay consistent. - **Follow-up after the order**: Set a reminder to follow up on delivery or customer satisfaction. ## Frequently asked questions ### Can an order be linked to a conversation? Yes. The order stays linked to the conversation and the customer record. ### Does it support online payment? Contact us to learn which payment options are currently available. ### Can I see orders by channel? Order data helps you read and compare channel results. ### Can an order be edited? The team can update an order according to the permissions it has. --- # How to sell on WhatsApp in an organized way Source: https://fihrist.world/en/blog/how-to-sell-on-whatsapp-organized Published: 2026-11-15 | Reading time: 9 min | Publisher: FIHRIST > WhatsApp made selling easy, but it was not built to manage sales. As messages grow, an order gets lost between a photo, a voice note, and a price question. This guide turns the work into clear steps, and explains what to do when something slips. ## Why sales get lost on WhatsApp The problem is not the app itself. Everything lives in one long thread: the question, the photo, the voice note, the agreement, the address, the size change, all consecutive messages in the same place. Two days later nobody remembers exactly what was agreed, who replied to whom, or whether the amount included delivery. Four symptoms usually show up. First: a customer asked and never got a reply, because the message sank under others. Second: an order was agreed and never recorded, then forgotten. Third: an old customer nobody contacted for months, even though they were happy. Fourth: two similar orders whose details got mixed, so a wrong size shipped. Each step below treats one or more of these. ## Five decisions before you send a single message Before organizing, settle five things. Most chaos comes not from too much work but from postponed decisions the team reopens every day. 1. Where the order is written: one place only, not two. 2. Who answers what: who owns price questions, who owns complaints, who owns delivery. 3. When you reply: will you let a message wait half a day during working hours? Write the limit down. 4. How payment works: the accepted methods, and what you write at confirmation. 5. The exchange policy: one sentence the customer understands, sent before closing the order, not after. ## Step 1: the chat is for talking, the record is for deciding The most important rule of the whole system: the order does not live in the chat. The chat is for conversation, photos, and questions. The record is for decisions. When the two roles mix, the chat becomes an archive you cannot search. Pick one place only, a notebook, a sheet, or a system, and write every order with the same fields every time: customer name and a reachable number, the product with its size, color, or option, quantity, the agreed amount including delivery or not, payment method, address and delivery method, the agreement date and expected delivery date, and order status. Why the same fields every time? Because comparison needs sameness. If you put the address in the notes once and in its own column the next time, you cannot filter the orders that have not shipped yet. Fixed fields are what turn a log into a working tool instead of an archive. ## Step 2: one template for taking an order The easiest way to prevent mistakes is to read the order back to the customer in one message before you act on it. This template is enough, change only the details: "Confirmed order: white linen shirt, size M, quantity 2, at the agreed amount including delivery, cash on delivery, address: ..., expected delivery Tuesday. Is this correct?" The customer reads what you understood, and corrects before shipping rather than after. Then copy the same message into your log. A message saved in the app keeps the words, but it does not gather the order into a row you can return to two weeks later. ## Step 3: five ready replies cover most chats Collect the questions you hear every day and write a short reply to each in your own voice, not a corporate voice. The goal is not robotic replies, but not typing the same sentence fifty times and getting one of them wrong. - Price: state the amount and what it includes in one line, then ask a question that opens the next step: would you prefer cash on delivery or a transfer? - Availability: name the options that actually exist, not all options: size M is available in white and navy. Shall I send photos of both? - Delivery: state the time, the area, and tracking if you have it, then ask for the full address. - Exchanges: one sentence: exchanges are accepted within a set period if the tag is still attached. Do not explain the whole policy unless asked. - Apologizing for a sold out item: offer an alternative, a restock date, or a refund, and pick one, not three. Keep these replies where the whole team can reach them, in a notes app or a shared file. When someone new joins, they start from a ready phrasing instead of inventing a new style. ## Step 4: one owner and one status per chat If more than one person is involved, the most dangerous thing is two people each assuming the other replied, while the customer waits for hours for no reason. The fix is simple: every chat has one named owner and one clear status. - Waiting for us: the last message is from the customer. This is the first list you open in the morning. - Waiting for the customer: the last message is yours. It needs a follow-up date, or it gets forgotten. - Closed: sold, declined, or the conversation stopped. It closes with a written reason, not with silence. When you hand a chat to a colleague, write it in the chat itself: handed this chat to a colleague, the next step is sending the photos. A short message preserves context better than any meeting. ## Step 5: set the follow-up date at the first reply Many sales are not lost to a clear no, but to silence. A customer asked the price then vanished, you assumed they were not interested, and in fact they got busy or are waiting on someone else. Set the follow-up date at the moment they ask, not when you remember. A practical rule: for quick decision items, follow up the next day. For more expensive items, unusual sizes, or customers waiting on a partner, follow up in three days. If two or three attempts bring no reply, close the case with a polite message that leaves the door open. ## A worked example: three orders in one day Example: a small clothing store gets three chats in one morning. First: a customer asks about a dress, asks about sizes, then goes quiet. Second: a customer confirms two shirts in different sizes, then comes back an hour later asking to change one of the sizes. Third: a customer wants to exchange an item that arrived too small. Without a log, this usually happens: the second order is prepared in the first size because the change came in a voice note nobody heard, the third order is forgotten because an exchange is not a new sale so nobody recorded it, and the first customer is never contacted again because her name appears on no list. Three chances lost in one day, not from bad intent but from the absence of one place where the truth lives. With a log, the picture changes: three rows, each with a status. The second row carries a note: size changed from L to M after confirmation, so the right item is prepared. The third row carries a clear type, exchange, not a new sale, with a reason. The first row carries a follow-up date of tomorrow. The difference is not the number of messages, it is that every fact now has one home. ## Common mistakes and how to fix them - Postponing the entry to the end of the day: write the row during the chat. Writing two hours later depends on memory, and memory trims and improves the details without you noticing. - The price in one place and the discount in another: make the agreed amount one field, and note beside it what it includes and what it does not. - Relying on pinned messages: pinning works for one policy. The rest needs a log or a shared file. - Replying to everything instantly, even late at night: set clear reply hours, and outside them send a message saying when you are back. Explained silence beats a late, tired reply. - Not recording why an order was cancelled: one word, price, size, or delivery, is enough to know what to fix next month. - Sending photos from the gallery from scratch every time: prepare one album per product and always send the same photos. - Ignoring the person who said they will think about it: this is the person who most deserves a follow-up, because they did not say no. ## A checklist: daily and weekly A short list works better than a complex system nobody opens. Five minutes in the morning and fifteen minutes a week is enough to start. - Every morning: open the waiting for us list and start there. - Every new order: write the row in the log before you close the chat. - Every promised date: review who you promised today, and send one honest message if you are late. - Every finished chat: close it with a status and a reason, do not leave it open. - Weekly: how many new chats arrived, and how many turned into an order? - Weekly: which question repeated most? Move it into the product description or a ready reply. - Weekly: who waited more than a day for a reply? - Weekly: what was the most repeated reason for cancellation? ## If this happens, do that - If the same product question comes up three times in a week, the problem is the description, not the customer. Add the missing detail to the post or listing. - If the customer says the amount is high, do not discount immediately. Ask: is the issue the amount, or the comparison with another product? Then offer an option or explain the difference. - If goods are late, tell the customer before they ask. Taking the initiative protects trust better than a late apology. - If you quoted the wrong amount, correct it in the same chat with the right figure, and do not wait for the customer to notice. - If you are answering forty chats a day alone, do not only look for better organization, decide what can wait and what cannot. - If an order is lost completely, write the cause in the log. A mistake that is not written down repeats. - If the customer sends details in batches, send the confirmation template at the end instead of assembling the details from ten messages. ## Where a tool like FIHRIST helps All of the above works with a notebook and discipline, and that is the important part. A tool speeds up the work, it does not fix a bad habit: if the order has no single home, no system will save it. As chats multiply, linking things by hand gets tiring. FIHRIST brings WhatsApp, Messenger, Instagram, email, and web chat into one inbox, links each conversation to the customer, product, and order, lets you assign an owner and a status to each chat, and provides reminders and follow-up rules that can be turned off. Permissions can be set per member, and it works in Arabic and English. Start with the steps above first. Try a week with a notebook or a sheet, learn where you actually stumble, then choose the tool that fixes that point. ## Frequently asked questions ### Do I need a WhatsApp Business account to organize sales? No, the organization itself works with a normal account and a notebook. The business account helps with things like quick replies and chat labels, while connecting WhatsApp to an outside tool usually needs the official business interface. Start with the organization, then decide whether you need the business account. ### How many follow-up messages before I stop? Two or three attempts with sensible gaps is enough in most cases, then close the case with a polite message. Repeating with no new reason does more harm than good. Return to the customer only when there is something real: an item is back in stock, new information, or a question that makes the decision easier. ### Should I reply to customers outside working hours? The decision is yours, but it should be announced. If you decide not to reply outside working hours, leave a message saying when you are back, which is better than unexplained silence. Some stores choose to answer only quick questions and postpone anything detailed to the morning. ### How do I record an order whose details arrived across many messages? Do not assemble the details from ten messages. Send the confirmation template at the end and ask the customer to correct anything wrong. Then copy the same template into the log, so the row and the message match. This cuts mistakes and saves time in later reviews. ### What is the first step if I have hundreds of old chats? Do not try to move all of them, you will stop halfway. Start from today: every new chat gets recorded, and any old chat that really needs follow-up gets recorded on its own. After two weeks you will have a real log of your current work, which is more useful than a partial archive. --- # How to track inventory in a small store Source: https://fihrist.world/en/blog/inventory-tracking-for-small-stores Published: 2026-11-15 | Reading time: 8 min | Publisher: FIHRIST > You do not need complex software to know what you have. You need one rule applied daily: everything that comes in and goes out gets recorded, and the unit is what you actually sell, not what you call it. This guide explains the rule and how to apply it in a small store. ## Why inventory tracking fails in small stores Three causes repeat. First: the unit is not defined, so the product is recorded as a whole while it sells by size. Second: recording is late, so the owner sees a number that does not match the shelf. Third: numbers are spread across a notebook, a cashier, and chats, so each place tells its own story. The result is that counting becomes a surprise: what you thought was there is gone, and what you thought was slow has sold out. The cure is not more expensive software, it is a clear definition and movement recorded on time. ## Step 1: define the unit before anything else A blue shirt in size M is not the same as a blue shirt in size L, nor the same as the navy one. If you write blue shirt: twenty pieces, you know a number but not an answer. The question you will get tomorrow is: do you have size L in blue? The total cannot answer it. The unit is the smallest thing you sell separately: the product with its option. In clothing: the item, the size, and the color. In shoes: the model and the size. In skin care: the bottle by volume. Sit down once and write your units, then use the same naming everywhere, in the listing, in the chat, and in the record. ## Step 2: five columns are enough You do not need a sheet with twenty columns. Five are enough to start: the unit name, the current quantity, the minimum level, the last movement and its date, and a short note. The last column is the most neglected and the most useful, because it holds the reason for an adjustment, the supplier name, or a packing note. If you use a spreadsheet, make one row per unit, not per product. Build the name in the same order every time: item, then color, then size. A fixed order prevents the same unit appearing twice in two spellings, a mistake that consumes search time and spoils totals. ## Step 3: record only three movements - In: goods arrived from the supplier. Record the actual quantity, not the ordered one, and if it came short write the difference the same day. - Out: a sale. Each sale deducts from its own unit, meaning the specific size and color. - Adjustment: damaged, lost, or returned, with the reason written in a word or a sentence. Every movement needs a date. The date is what later lets you ask: what happened this week? Without a date the record becomes a single picture, and a picture does not tell movement. ## Step 4: deduct at agreement, not at delivery The most common cause of double selling is late recording. If you deduct at delivery, the quantity you see during a chat is stale, and you may promise a customer an item a colleague sold a minute ago. Deducting at confirmation means the quantity is reserved. If the customer cancels, return it with a recorded adjustment and the reason. This keeps the equation clear: what you see is what you can sell now. ## Step 5: minimum levels without magic numbers The minimum is the quantity at which you reorder. No single number fits everyone, but there is a way to reach yours: take your supplier lead time, add a margin for the days they usually run late, then work out how many of that unit you sell in that window. Example: a supplier delivers in ten days, and the unit sells about three pieces a week, so expected sales in that window are about four or five pieces. Set the minimum at five or six, then adjust after three weeks against reality. The first number is an estimate, the number after a month is experience. Do not set a minimum for everything on day one. Start with the fastest movers, because running out of them costs you a real sale, while a delayed slow item costs you nothing. ## Step 6: count, do not guess 1. Pick a quiet time and pause selling while counting if you can. 2. Count the units by hand, by size and color, not from memory and not from the supplier invoice. 3. Compare with the number in the record and log any difference as an adjustment with a reason. 4. If the difference keeps recurring on one unit, look for the cause: a recording error, unrecorded damage, or something else worth reviewing. For small stores, a weekly partial count of the fastest movers and a full count monthly is enough. A full count every day wastes time, and an annual count alone comes far too late. ## A worked example: a clothing store and three events Example: one unit, a white linen shirt in size M, has six pieces in the record, and the minimum is three. A single day brings three small events. 1. First order: two pieces of that unit. Four remain. 2. Second order: one piece. Three remain, which is the minimum, so the supplier order is written that same day, not when the shelf is empty. 3. A return from another unit, a white shirt in size L: it goes back to its own unit, not to size M. Mixing them here is common and spoils both numbers. Then the count comes at the end of the week and finds two pieces of M on the shelf instead of three. The difference is one piece, unrecorded damage. An adjustment is written with the reason damage, so the number becomes two, which is below the minimum, and the next action becomes obvious: reorder, or stop promising that unit until it arrives. Notice that nothing exceptional happened that day. Three small events, and the number still moved from six to two, and the decision moved with it. That is what tracking means: a decision that changes with the number, not a number written down for the record. ## Step 7: read movement, not just quantity Quantity tells you what you have, movement tells you what to do. A unit with twenty pieces may be excellent if it sells, and a problem if it has not moved for two months, because money is trapped in it. Compare sales across two periods for the same unit, and ask two questions: what moves fast and needs reordering? What has not moved and needs a decision? The decision may be a promotion, a bundle with another product, or stopping the purchase in the next order. The third is the hardest and the most useful. ## Common mistakes and how to fix them - Recording the product as a whole instead of by unit: start now by separating the sizes that actually sell, and leave the rest in one row for the moment. - Postponing the deduction to the end of the day: deduct at confirmation. If you cannot, write the order in a draft and finish it before closing. - Returns with no reason: one word, size, defect, or changed mind, is enough. - Copying numbers by hand between a notebook and a cashier: manual copying is the biggest source of errors, and the fix is one stock number everyone reads. - Treating the supplier invoice as the record: the invoice says what you ordered, not what you received. Record what actually arrived. - Different names for the same unit: white shirt M and white linen shirt medium become two items in the record and one unit in reality. Fix the naming. - Buying slow items because they are cheap: a low price does not justify piling stock, especially when capital is limited. ## If this happens, do that - If the count never matches the record on one unit, the problem is recording, not theft. Review who sells that unit and when they write it down. - If goods arrive short, log the difference as an adjustment with the reason supplier shortfall, and claim it the same day with a photo of the invoice. - If a unit runs out faster than expected, do not only fix the number, raise its minimum level. - If units look very similar, such as the same color under different brand names, use a short code per unit, or a card with a QR code. - If your business is a service or tailoring, stock sits on materials, not on the finished piece. Define the unit by what it actually consumes. - If you sell from more than one place, the rule is the same: one shared number, and each movement recorded once. - If you do not know where to start, pick ten items only. Ten items recorded accurately are more useful than a hundred recorded halfway. ## Where a tool like FIHRIST helps All of the above works with a notebook and a sheet, and the principle does not change with the tool: a clear unit, recorded movement, and one number everyone reads. As units and orders multiply, updating by hand gets tiring. In FIHRIST, sizes, colors, and options are recorded as separate stock units, each with its own price and quantity, every order deducts the quantity sold, an item can be identified with a QR code, and item movement can be compared across periods. Permissions can be set for each team member. The advice stays the same: start with ten items and one month of discipline, before you move to a tool or to a bigger stock. ## Frequently asked questions ### Do I need a barcode or QR code to start tracking stock? No, you can start with consistent names and a number written on the tag. Barcodes and QR codes help when units multiply or more than one person sells, because they reduce the chance of picking the wrong unit. Start with consistent naming, and add the code when manual searching becomes slow. ### How often should I count stock? A weekly partial count of the fastest movers and a full monthly count suits most small stores. A full count every day wastes time, and an annual count is far too late to correct errors. Adjust the frequency to how fast your items move. ### How do I record a return in stock? Log it as an adjustment that returns the quantity to its original unit, with a short reason: size, defect, or changed mind. Do not return it to another unit even if the product is similar, because that spoils two numbers at once. If the piece cannot be sold, record it as damaged and do not put it back into available stock. ### Which is better, a notebook or a spreadsheet? A notebook is faster at the start and needs no charging or training, but a spreadsheet makes totals, period comparisons, and searching for a unit easier. What matters more than the medium is that there is one place everyone writes in, and that movement is recorded on time. Many stores start with a notebook and move to a sheet as the count grows. ### How do I find the items that do not move? For each unit, record the date of the last sale. Any unit with a month of no movement is a candidate for a decision: a promotion, a bundle with another product, or stopping the purchase. Do not rely on instinct, slow items hide on the shelf and get forgotten. --- # The difference between a CRM and an order log Source: https://fihrist.world/en/blog/crm-vs-order-log-difference Published: 2026-11-15 | Reading time: 8 min | Publisher: FIHRIST > Many people assume they are the same thing, because both "record customers". In fact each answers a different question, and confusing them ends either in a tool that gets bought and never used, or in a store that grows without memory. This guide separates them with a worked example, then gives you a decision rule. ## The difference in one line An order log asks: what did we sell? A CRM asks: who bought, and what is the next step with them? The first keeps the transaction, the second keeps the relationship. A store that knows its sales but not its customers sells once to each person and then starts from zero, and a store that knows its customers but not its numbers cannot tell which item deserves a reorder or which month deserves preparation. ## What an order log is, and what it does well An order log is a set of rows, each row one transaction. The most important thing about it is that the columns are fixed: order date, customer name, product, quantity, price, and order status. Fixed columns are what turn a scattered notebook into a record whose questions can be asked and whose numbers can be totalled. - Knowing what must be prepared today: every row marked "confirmed" that has not shipped. - Knowing what was delivered and what was not, so no order sits pending without follow-up. - Totalling a week or a month with a simple sum on the price column. - Spotting the most requested items from repeated product names in the rows. - Going back to an agreed price when a customer disputes it. A small worked example: this week you have only four rows. Two are marked "confirmed" and not shipped, one is "shipped", and one is "delivered". One glance tells you that two orders need preparing today. That is all the log does, and it is not a small thing, because many small stores carry their orders in their head and then forget one. ## Where an order log stops The log answers well about the transaction and stops at the person. If you ask: "this customer, did they buy before? What did they buy? Did I promise them anything?" manual searching begins: sort rows by name, read each row, then try to recall the conversation. And if the name was written in two different ways, which always happens, you may find two rows and miss the third. The second problem is that the log has no future. All its columns describe what happened. No column answers: when do I speak to them again? Who owns them? What are they waiting for? So follow-up lives in the owner memory, and the owner memory is the first thing to wear out when messages pile up. ## What a CRM is, and what it does well A CRM (customer relationship management) system is one record per person, not per transaction. That small difference changes how work happens. Inside a customer page you find their details, conversations, orders, your notes about them, and the agreed next step. Anything that ever happened with them sits in one place, because you look up the person first and then see the whole history. - A quick answer to "who is this?" before you type the first word of a reply. - Knowing who bought more than once, and who bought once and stopped, without manual sorting. - A clear follow-up date for each customer, stored where someone else can see it too. - One named owner per customer, so two people do not ask the customer the same thing and nobody is forgotten. - Handing a customer from one employee to another without the second starting from zero. A CRM does not cancel orders, it shows them in context: the order is still a row, but linked to a person whose history you know. The question is not which tool is better in the abstract, but whether the numbers and the people sit in the same place or in two places that never meet. ## The real difference: unit of work and time If you want one rule to remember, it is that the unit of work differs. In a log the unit is the order, in a CRM the unit is the customer. Every other difference in time, purpose, and daily use follows from this one. - Unit: a transaction row in a log, a person page in a CRM. - Time: past and present in a log, the future (follow-up) in a CRM. - Question: "how much did we sell?" versus "what is the next step with this customer?" - Daily use: packing and shipping in the log, replying and convincing in the CRM. - Who uses it: whoever prepares orders in the log, whoever talks to customers in the CRM. This does not mean one ranks above the other. A store selling one item once to each customer needs a clean log rather than relationship management, and a store that lives on returning customers needs both, linked rather than separate. ## A worked example on the same data Imagine a small clothing store. A customer messaged two months ago asking about a dress in a specific size, and you told her that size was out of stock. Two weeks later she came back asking the price of another piece and did not complete. Then she bought one small item once. Three interactions and one order, that is all that happened. In the order log you will find only one row, because nothing before the purchase became an order. The two messages live in the chat and may be buried under dozens of messages a week later. The result is that you see a customer who bought once, and that is all you know about her when a new message arrives. In a CRM you see the same page: asked about an unavailable size, then asked a price and did not complete, then bought. Now the next step is obvious: when that size returns, tell her. And before that, one question clarifies why she stopped: was it the price, the size, or the timing? ## When a log is enough, and when you need a CRM Do not buy a tool because it is famous. Use the decision rules below, and apply them to your situation today, not to what you hope for in a year. The first rule saves you a subscription you will not use, the second saves you a year of lost orders. - A log is enough if most of your buyers buy once, and there are few enough each month that you know them by name. - It is enough if you alone reply and nobody shares the conversations with you. - You need a CRM if returning customers are a real part of your sales, not an exception. - You need one if more than one person replies, and it has happened that two replied to the same customer or nobody did. - You need one if you forget to follow up with people who asked and did not buy, or discover it a week later. A practical rule: if you found three or more items in the second list, you need a CRM, or at least an order system that behaves like one. If you found only one, fix the log first, because a CRM full of incomplete data is worse than a small correct log, and a tool does not create a habit that was never there. ## Common mistakes and how to fix them - Buying a CRM before tidying the log: the mess moves into a nicer tool. Fix: clean up the last two months of orders first, and migrate only what is correct. - A log with no status column: every row looks the same. Fix: add a status column with a few fixed options, and never type free sentences into it. - The name in different forms: first name once, first name plus initial once, a number with no name once. Fix: tie each customer to one phone number, and treat the number as the identifier. - Two separate systems: the log in a file, the chats on a phone, updating by hand. Fix: one place is the source of truth, every other place is a copy that is read, not edited. - A CRM used as an address book: names with no history and no next step. Fix: do not create a customer page without a clear reason to contact them later. - Follow-up kept in memory: the most dangerous and the most common. Fix: a written date or a reminder, and a short daily list that is read rather than remembered. ## How to link the two with any tool 1. Pick one identifier per customer, ideally the phone number because it rarely changes. 2. In the order log, make the customer column mandatory, and write the same number every time. 3. Add only two columns: order status, and next follow-up date. 4. Keep order status (new, confirmed, shipped, delivered) separate from conversation status (waiting for us, waiting for the customer, closed), because one is about the parcel and the other about the conversation. 5. Create a short page per customer that does not duplicate data but collects links to their orders and one latest note. 6. Set a fixed weekly review: who is waiting for a reply, who is waiting for a follow-up, and which question repeated most. These steps work on a simple sheet, and some of them work in a notebook if the volume is small. What matters is one identifier and a written follow-up date, because what fails most in small stores is not the choice of tool, but that the information exists and nobody sees it at the right moment. ## The minimum fields, and a template you can copy You do not need twenty fields. Many fields get abandoned, and a field that is never filled is worse than a missing one because it convinces you that you have information. Start with the minimum that answers both questions: what did we sell, and who bought. - Customer card: one canonical name, and one phone number. - How they reached you: WhatsApp, Instagram, a referral, a store visit. - Last contact, and a short note about its outcome rather than its content. - The next step, its date, and who owns it. - Order card: order number and date, and the customer phone number. - The product with size, color, or option, the quantity, and the agreed price. - Status, delivery method, and any note that saves asking the customer again. Keep this list in front of you for two weeks, then delete any field you never used and add any field you needed and did not have. ## If this happens, do that - If the log total disagrees with the cash drawer, treat the drawer as the truth at the moment of sale, update the log the same day, then look for the cause in the last three rows before blaming anyone. - If a customer keeps asking about their order status, the problem is status visibility, not the customer: send a short message at every change. - If you find a customer with more than one record, merge the old into the newer, keep one number, and move the old history across as a note instead of deleting it. - If the team stops filling in the CRM, cut the fields to three and remind them the goal is faster replies, not surveillance, because feeling watched is what stops data entry. - If follow-up is always forgotten, make it a ten minute morning task, not a promise. - If you do not know where to start, take only the last thirty orders and convert them to the new shape. Next month will build on that foundation alone. ## Where FIHRIST fits into this All of the above can be done with a sheet, a notebook, and discipline. The need for a tool appears when linking by hand becomes slower than selling. That is where FIHRIST comes in, as a tool and not a substitute for organization: it brings WhatsApp, Messenger, Instagram, email, and web chat conversations into one inbox, links each conversation to the customer, product, and order record, lets you assign an owner and a status to each conversation, and sets reminders and follow-up rules that can be turned off, with permissions per team member. It works in Arabic and English, and the channels available depend on what you connect. But if you work alone with thirty orders a month, a clean log and a written follow-up date may be enough. Start with the steps, then choose the tool that reduces the manual work you actually suffer from, not the manual work that bothers you in theory. ## Frequently asked questions ### Is a CRM the same as an order log? No. An order log keeps the transaction, a CRM keeps the customer, their history, and the next step with them. Many systems combine both in one screen, but the difference in the question each answers still matters when choosing, because a tool that answers a question you do not have will not get used. ### Does a very small store need a CRM? Not necessarily. If most of your customers buy once and you are the only one replying, a tidy order log with a status column and a follow-up date is entirely enough. The need appears when returning customers become part of your sales, or when someone shares the replying and duplication or silence starts to happen. ### What is the first field to add to an order sheet? A status column with fixed options: new, confirmed, shipped, delivered. It is the cheapest addition and the most useful, because it turns the sheet from an archive into a work list that tells you what to prepare today. Add the follow-up date after it, then stop, because too many fields get abandoned. ### How do I link orders to customers without a big system? Use the phone number as a single identifier, write it in the same format in every row, then add two columns: follow-up date and owner. That lets you see one person history by sorting rows on their number, and that alone solves most of the scatter problem in small stores. ### Can a spreadsheet itself be a CRM? It can be a start, provided you collect contact history and the next step in it, not only orders, and you open it every day. But sheets get hard when more than one person edits them at the same time, and it is hard to see a customer conversation beside their order. --- # How to reply to customers faster Source: https://fihrist.world/en/blog/reply-to-customers-faster-unified-inbox Published: 2026-11-15 | Reading time: 9 min | Publisher: FIHRIST > Reply speed often decides the sale, not because the customer is always in a hurry, but because they message three stores in the same minute and lean toward whoever answers first with something useful. The problem is that a large part of your time goes not into typing, but into searching, switching, and checking. This guide breaks a reply into steps, then shortens each step. ## Reply speed is not typing speed When we say a store replies fast, we do not mean its owner types fast. We mean the path between a message arriving and a reply appearing is short. That path has small repeated steps: open the app, see who wrote, try to recall who they are, look up their previous order, ask a colleague whether they replied, assemble the answer, then type. None of these steps takes more than a minute, which is why you do not notice them. But they repeat with every message. If a single message costs you five minutes of preparation and one minute of typing, you are not slow at replying, you are slow at preparing. Shortening the preparation is what changes the customer perception of speed. ## Where the time really goes A small worked example, claiming no realism for anyone else situation. Imagine you receive twenty messages in a day. Each time you stop current work to open another app, then return to what you were doing. The interruption itself, not the reply, is the hidden cost: every return needs a minute to regain focus. Twenty interruptions means twenty minutes of lost focus, and that is on a quiet day. - Switching between apps to see who wrote, and forgetting a whole channel because it is out of sight. - Looking up the customer or their previous order before answering, and this lookup is usually the longest part. - Not knowing whether a teammate replied, so you ask them, they say they did, and two messages are wasted on one question. - Retyping the same answer to repeated questions, with a slight change in wording each time. - Replying at the wrong time because the message arrived at a busy moment and was then forgotten. Note that only one of these items relates to typing. The rest is organization. That is why buying a faster app solves nothing if the information is split across three places: you are moving the slowness from one place to another. ## Step 1: bring the channels into one place The number of channels you open each morning is the number of chances to forget one. A unified inbox shows all messages in one list, sorted by newest or by what is waiting for a reply, so you start your day in one window instead of five. The idea is not technical, it is that every message becomes visible to you at the same moment. If you do not have a unified inbox, start with a middle solution: make one channel the main one, state in your profile on the other channels that orders are completed there, then check the secondary channels at two fixed times a day. This is less efficient than a unified inbox, but far better than checking at random. ## Step 2: show customer context beside the message The slowest part of replying is the silent question: who is this, and what did they order before? If the name and past orders appear beside the message, replying becomes writing instead of searching. This also reduces mistakes, because you do not apologize to a customer for an item they already bought, nor ask again something they answered. The minimum you need beside a message is three things: the name, the last order if any, and a short note from the last contact. With those three you write a fitting reply in most cases. Any extra information is nice, but it is not a condition to start. ## Step 3: assign an owner and a status to every conversation When each conversation has a name on it, the question "did anyone reply?" disappears, and with it the worst kind of mistake: two people each assuming the other replied, so nobody does. You can also see quickly what is waiting for a reply and who owns it, instead of opening every conversation to find out. - Status "waiting for us": this is your first list in the morning, and it is where speed is actually measured. - Status "waiting for the customer": needs one check a day, not constant watching. - Status "closed": a conversation that ended with a clear outcome, an order, a no, or a handover. Do not close without an outcome. - Status "needs a decision": the customer asked something you cannot answer, so it goes immediately to whoever can. A simple team rule: do not close a conversation whose outcome you do not know. Closing without an outcome makes the numbers false and makes the conversation return a week later as if new, so the customer asks the same thing again and gets a different answer. ## Step 4: prepare repeated replies, not automatic ones Collect the questions that repeat weekly and write one good answer to each, then adapt it per customer instead of writing from scratch. The difference between a template and an automatic reply is that a template is a starting point you write from, while an automatic reply is sent without reading. The first speeds you up, the second makes the customer feel they are talking to a wall. The questions that deserve a template are usually five: the final price including delivery, availability in a size or color, delivery time, payment methods, and the exchange policy. Write only two sentences for each. A long message gets half read, a short one gets read fully. - Price: "The item is X, delivery is Y, so the total is Z. Send me the name and address if you would like me to prepare it." - Availability: "It is available in the size you asked about now, and the quantity is limited. Shall I hold it for you?" - Delivery: "Delivery inside the city usually takes X working days, outside it Y. Send me the address and I will check precisely." - Out of stock: "This size is not available right now. I have a close alternative or I can tell you when it arrives, which do you prefer?" When using a template, change at least the first sentence so it is specific to this customer. One sentence tied to what they said is enough for them to know you read their message, and that prevents the feeling of a canned reply more than anything else. ## Step 5: set a realistic reply-time goal and measure it Pick a goal that suits your product, not one you admire in an article. An item bought after long thought may tolerate a reply two hours later, an item ordered on impulse may not. What matters is that the goal is written, known to everyone who replies, and that you define the working hours it is measured in. Then measure only one thing at first: how many conversations went a working day without a reply. Do not measure the average, because an average hides the bad cases that lose customers. The case that waited two days matters more than ten cases answered in a minute. 1. Write the goal where the team can see it, along with the working hours. 2. Review the "waiting for us" list weekly and pull out what exceeded the goal. 3. Ask about the cause, not the culprit: missing information, a busy peak, or a message that arrived outside working hours. 4. Fix one cause each week, and do not try to fix everything at once. An unrealistic goal is worse than no goal, because it makes the team stop measuring or start hiding the late cases. Choose a goal you can meet in an ordinary week, then tighten it gradually once it holds. ## Step 6: share the load when there is more than one person Having more than one person does not automatically speed up replies, and can slow them down. The rule is that every conversation must have one owner at any moment, even if the owner changes later. When the owner is shared, there is no owner. - Split by channel or question type, not by mood: who answers inquiries, who follows up confirmed orders. - Give each member only the permissions they need, so someone who needs pricing data does not see all customer data. - Make the person replying able to see availability and price themselves, since every question routed to someone else becomes a delay. Clear permissions are not only an administrative matter. If the person replying cannot see the information, they will go and ask, they will wait, and the reply will be late. Permissions are part of reply speed, because they determine whether the answer is one click away or one internal conversation away. ## Common mistakes that block speed - Replying to every message instantly: it makes you permanently available, so real work stops. Fixed review times and working the queue in order are better. - Relying on notifications: a notification interrupts you, then you forget the message once you dismiss it. Working from a list beats working from a notification. - A reply with no question: "done" or "sure" ends your message without moving the conversation. Every good reply contains one question or one new piece of information. - Automatic replies to everything: they stop the customer at the first step when they want a specific answer. Keep it to clarifying the next step only. - Many channels with no review time: a channel you do not review is a channel you do not own. - Closing a conversation after sending a price: the most sensitive moment is right after a price, and that is where follow-up belongs. ## If this happens, do that - If customers write on a channel you do not watch, add it to review time or close it officially and state the alternative in its profile. - If a message arrives at bedtime, send one line fixing the time: "I saw your message, I will reply in detail in the morning." This calms the customer more than a tired, incomplete reply. - If one question repeats a lot, the error is elsewhere: add the answer to the product description or the ready replies. - If a customer keeps asking about order status, send an update at every change without being asked. - If replies lag at a known peak time, assign who leaves their task to cover messages for that hour only. - If you forget a reply after getting busy, give every message the status "waiting for us" until it is closed by a reply or a handover. ## A short checklist before you start 1. List the channels customers actually use to reach you, and whether all are reviewed or some are forgotten. 2. Set two fixed review times in the working day, even if you have not gathered the channels yet. 3. Write five short templates for repeated questions, two sentences each. 4. Add an owner and a status to every conversation, and start with the "waiting for us" list. 5. Choose one reply-time goal, and measure weekly how many cases exceeded it. 6. Review after a month: which step added time without benefit? Remove it. ## How FIHRIST helps here The above can be done by hand, but coordinating manually between a channel, a record, and a conversation becomes slower than the reply itself when messages pile up. That is where FIHRIST comes in as a tool: it brings WhatsApp, Messenger, Instagram, email, and web chat into one inbox, links each conversation to the customer, product, and order record, lets you assign an owner and a status to each conversation, and sets reminders and follow-up rules that can be turned off, with permissions per team member. It works in Arabic and English, and the channels available depend on what you connect. Start with the steps first: the two review times, the five templates, and the "waiting for us" list. Those three work with no tool at all, and they are what makes the difference in the first week. The tool comes after them to reduce manual work, not to create a habit that was never there. ## Frequently asked questions ### Does a unified inbox reply to customers for me? No, it gathers messages and puts the customer context beside them so your reply is faster and more accurate. The reply is still yours. Some tools include an assistant that answers from store data when you enable it, but it stays under the team supervision, and the team can step in on any conversation. ### How long should a reply take? There is no number that fits every store. Pick a goal that suits your product and working hours, write it where the team sees it, then measure how many conversations exceeded it rather than the average. The few late cases are what lose customers, and an average hides them. ### What is the fastest improvement I can apply today? One list called "waiting for us", reviewed twice a day at two fixed times. That list alone prevents a message from being buried under newer ones, and it is the cheapest step with the largest effect, needing no tool at all. ### How do I stop two people replying to the same customer? Give every conversation one owner written by name, and agree that the named person replies until the conversation is handed over with a clear note. This solves the problem better than any alert, because an alert can be read and forgotten, while a name prevents the confusion at the source. ### Do ready replies make a store feel impersonal? It can happen if they are sent as-is every time. The fix is to open the reply with one sentence tied to what the customer actually said, then use the template for the precise information. That saves time and makes the customer feel read, not processed. --- # How to follow up with the customer who went quiet Source: https://fihrist.world/en/blog/follow-up-customers-who-went-quiet Published: 2026-11-15 | Reading time: 8 min | Publisher: FIHRIST > A silent customer is not necessarily a no. Often they got busy, forgot, or are waiting on someone else. What separates a follow-up that wins the sale back from one that loses the customer is timing, reason, and wording. This guide puts the three in order. ## Why does the customer go quiet? Four different reasons From outside, silence looks like one thing: no reply. Under it are different reasons: a customer who got busy and forgot, one waiting on someone else, one who found an alternative and could not say so, and one who did not understand the next step after the price. Each needs a different message, which is why one message for everyone fails. A small example: three customers asked the price of a bag on one day. The first got busy after the first message. The second is waiting for a partner. The third found it cheaper elsewhere. If you send all three "are you still interested?" you have sent a message that fits one of them, usually the one that goes unread. A fifth reason deserves admitting: you. A long message with no question, a late reply, or a price that changed twice in a week all make the customer withdraw quietly. Before you blame them, read your last message. ## Before you send: prepare the file in two minutes Most bad follow-ups happen because the seller no longer remembers what they promised. They send a general question, the customer replies with a question nobody can answer any more, and the conversation ends there. Two minutes before the message save a whole conversation. 1. Read the last ten messages in the chat quickly, not everything. 2. Write in one line what the customer asked for and what exactly you promised. 3. Check that the item is available and its price today, because the old price may no longer be right. 4. Decide the goal of the message: a reservation, an answer to a question, or a polite close? If you cannot state the goal of the message clearly, do not send it today. A message with no goal reads as noise and teaches the customer to ignore your next ones. ## Rule one: no follow-up without a reason "Any news?" moves all the effort to the customer and asks them to remember why the conversation existed. A good message carries something they do not know: availability, a confirmed price, an alternative, or a date. Replying becomes easy, because answering information is easier than answering a reminder. - Availability: the size or color they asked about is back in stock. - A confirmed or changed price: tell them yourself instead of letting them find out late. - An alternative: another color, a close size, or a model that does the same job. - An arrival date: if the item is out of stock, a specific date is reason enough to reach out. - A close: with no real reason, the last message makes clear you are stopping. ## The follow-up schedule: when to send and what to expect The timings below are a starting point, not a law. Adjust them to your product cycle: a small item is decided within an hour, a piece of furniture can take two weeks. What matters is that every conversation has a written next date. 1. At the first question: record the date before you close the chat, what is not written now will not be remembered tomorrow. 2. After one day: for quick questions that ended with no reply, a short message carrying one piece of information. 3. After three days: for orders that reached price or size and then stopped. 4. After a week: for bigger purchases that need advice or a comparison between options. 5. Two days after delivery: a check on the product itself, not a new offer. 6. After thirty days: for the happy customer, tied to a related purchase. 7. After two or three months: for the old customer, with a new reason only. This schedule spreads conversations across days so each message lands on time, it does not ask you to be in the same chat daily. The common mistake is three messages in two days then a month of silence. ## Message templates by situation The templates below are drafts, change a word or two so they sound like you. Most important is picking the one that fits the situation, a good template in the wrong place does more harm than a plain message in the right one. - Silence after the price: "Hi, you asked about the black bag. Would you like me to clarify any detail before you decide? And if the price is the issue, tell me, I have more than one option." - Back in stock: "The item you asked about came back today. Shall I hold the quantity for you before it goes?" - After a promise: "As promised, the details came through. Two sizes are available now, at the price I gave you. Shall I prepare the order?" - Making the decision easier: "If the decision is hard, I can hold the piece for you for two days with no payment. Would you like that?" - Bigger purchases: "Before you decide, one question helps me recommend the right one: is this for daily use or for an occasion?" - After delivery: "Did the order arrive? I wanted to make sure the size is right, and if there is any problem tell me today." - Reactivation: "Hi, a new collection arrived close to what you bought before. Would you like me to send photos?" - Apologizing for our delay: "Sorry for the late reply. I reviewed your order now, and here is exactly where it stands. Shall we continue?" - A polite close: "I did not hear back, so I assume the timing is not right. I will stop following up, and if you need anything later, message me any time." The last template matters most, because it decides how the customer remembers you a month later. A respectful close brings them back on their own at the first need, while mutual silence leaves them thinking you lost interest. ## Tone: how to write a message that does not feel pushy Pushiness is not only about how many messages you send, it is about their shape. A long message with three questions and two apologies feels heavier than three short ones. The rules below are simple and clearly affect replies. - One to three sentences at most. A long message reads as pressure, a short one reads as service. - One question only. Two questions in one message usually mean zero replies, because the customer answers the easier one and leaves the rest. - Do not apologize three times. One apology when there was a real mistake, then move to the point. - Mention a detail that belongs to them: the size, the color, the product name. The detail says you remember them, not that you are messaging everyone. - Leave a clear exit: "if now is not the right time, tell me and I will stop". This reduces the feeling of being chased. - Do not open with a discount. A discount on the first follow-up teaches the customer to ignore you in order to get a lower price. Compare: "Are you completing the order?" asks for a decision from someone without enough details. "You asked about the black bag, it comes in two sizes and I can hold one for two days, want me to check what is available?" gives a small step and new information. ## When to stop: the three attempts rule Good follow-up is limited. The practical rule: three attempts, each with a different reason, then stop. Three messages saying the same thing in a week does not mean you are diligent, it means you are pushing, and the result is usually a block. - The customer explicitly asks you to stop: respect it immediately, with no discussion and no final attempt. - Three attempts with different reasons and no reply at all, not even one word. - Two refusals on price: do not repeat the same offer, the refusal is clear. - They say they bought elsewhere: thank them and leave the door open without a hint. - A month passed with no new reason: long silence needs an occasion, not a reminder. Stopping is not deleting the customer. Mark them "inactive" with the date of last contact and the reason for silence if you know it. Coming back needs a real reason: availability, a new product, or a season that concerns them. ## Common mistakes and how to fix them - The same message for everyone: keep only three templates and personalize each with the name and the product asked about. - Following up on one channel only: someone who read and ignored WhatsApp may answer a short call. - Opening with a discount: open with information and leave price negotiation for when they raise it. - A promise with no date: "I will get back to you" should become "I will send it on Tuesday". - Leaving follow-up to the end of the day: it is the first thing cancelled when busy. Use the first ten minutes. - Following up after a purchase with a sales pitch: after delivery ask about satisfaction, not about another order. - Forgetting the reason: log the reason, otherwise the message turns into a valueless generic reminder. ## If this happens, do this - If there is no reply after two attempts: send the polite close and set a date to return when there is a real new reason. - If they say "too expensive": do not cut the price at once. Ask what they are comparing it to, then suggest a smaller or simpler option if you have one. - If they say "I will get back to you": ask for a rough date, suggest one yourself, then record the date they agreed to. - If the message stays unread or you are blocked: do not try from another number. It destroys trust, and respect costs less than one sale. - If they return after three weeks: start where you stopped, and do not ask "do you remember your order?", that makes them start from scratch. - If they complain about a delivered item: the follow-up becomes problem solving. Listen, offer a fix or replacement, then return to selling later. - If they ask something you do not know: say "I will check and reply today", and keep that even if you find no answer. ## The routine: ten minutes every morning 1. Open the "follow up today" list before new chats. 2. Sort oldest first, someone who waited four days comes before one who waited an hour. 3. Send five to ten good messages, not thirty rushed ones. 4. After each message update the status: waiting for the customer, waiting for us, or closed. 5. Close any item with no clear reason and reschedule it when one appears. A simple list needs six fields: name, last contact, what they asked for, the reason for the next follow-up, its date, and the status. One sheet is enough, and what matters is updating it the same day, not at the end of the week. A checklist before every send: does it carry information or a choice? One question? A detail that belongs to them? A clear exit? If you answered "no" to any of these, rewrite it. ## A simple check: is follow-up working? You do not need complex reports. Every two weeks, count three numbers: how many follow-ups you sent, how many replies arrived, and how many turned into an order. These are enough to see where the problem is: wording, timing, or the offer. - Few replies, many messages: wording too long, timing too late, or no reason in the message. - Many replies and few orders: the problem is the price, the offer, or the way the order is completed, not the follow-up. - The reply always comes after the third: start there and save the first two. Change one thing at a time. If you change timing, wording, and offer together you will not know which one worked. ## Where a tool like FIHRIST helps Everything above can be done with a notebook, a sheet, and discipline, that is the way we recommend starting. But with many conversations, linking every customer to their record and dates becomes tiring manual work. In FIHRIST, WhatsApp, Messenger, Instagram, email, and web chat sit in one inbox, and each conversation is linked to the customer, product, and order, with an owner and a status. You can set a reminder or a follow-up rule, and every rule can be turned off, so you stay in control of what is sent. The interface works in Arabic and English. The tool organizes the list and the dates, but it does not write the message for you and does not know when the customer is busy. Judging tone and situation stays with you. ## Frequently asked questions ### How many times should I follow up before stopping? Two or three attempts is enough in most cases, provided each one carries a different reason: availability, information, or an alternative. If all three say the same thing they are one message repeated, and stopping is better for the relationship. After stopping, mark the customer inactive and return with a real new reason, not just because time passed. ### Should I follow up the same day or wait? If the item is a quick decision and the customer has time, wait at least one day, because following up within the hour feels like pressure. But if the customer asked a specific question and you do not have the answer yet, send it the same day because that completes the service rather than chasing it. The rule is to separate completing missing information from reminding someone about a decision they have not made. ### What should I write to a customer who asked the price and then vanished? Write one short message with new information and a single question. For example: "You asked about the black bag. It comes in two sizes and I can hold one for you for two days. Want me to check what is available?" Do not open with a discount or with "are you still interested" alone, because it moves the effort to the customer and tells them nothing. If there is no reply, send a second attempt with a different reason, then close politely. ### Is a discount a good way to bring back a quiet customer? A discount on the first follow-up teaches the customer to ignore you in order to get a lower price, and it lowers the value of the product in their eyes. Better to start with information, an option, or an easier decision, such as a free hold for a set period. If price is the real reason they will raise it or compare, and then a discount or a cheaper option is a logical answer rather than a gift. ### How do I follow up with an old customer who has not bought in months without annoying them? Tie the message to a reason that concerns them: an item close to what they bought, the return of something they asked about, or a season in which they use what they bought. One message every long while is better than repeated messages with no occasion. Make the exit easy with a line like "if the timing is not right, I am here when you need me", then do not reach out again until a new reason appears. --- # How to avoid selling an item that is out of stock Source: https://fihrist.world/en/blog/prevent-overselling-and-stockouts Published: 2026-11-15 | Reading time: 7 min | Publisher: FIHRIST > The worst moment in selling is apologizing to a customer who agreed on an order that no longer exists. The problem is rarely bad intent: it is usually an old number, an option that was never separated, or a promise made before anything was reserved. This guide treats the causes one by one. ## The difference between what you own and what you can sell This is where most of the mistake starts. The number in your head is not the quantity you can sell. What you can sell is what you own, minus what you promised someone else, minus what is damaged, minus what is held for an existing order. Whoever sells from the first number sells twice without knowing it. - Quantity on hand: everything in the storeroom or on the shelf, including what is reserved. - Reserved quantity: what was promised to a customer and not yet delivered. - Available quantity: on hand minus reserved minus damaged. This is the number you speak from. A small example: you have six black pieces in size M. A customer agreed on two that have not been delivered, and one piece is damaged but was never recorded. The real available number is three, not six. If this calculation is not clear in the record you will sell those two pieces twice, and the customer will discover the error, not you. ## Why does overselling happen? Five real causes 1. Sales are recorded late, so the number stays stale for hours or a day, and you sell from a number that was never updated. 2. The item exists in more than one place, in the shop, in front of you in a chat, and at the cashier, with no single shared number. 3. Sizes and colors are merged into one line, so you think you have twenty pieces when you have twenty of one size only. 4. No level warns you before it runs out, so you learn an item is gone the moment a customer asks for it. 5. A hold is promised but not written, so you give it to one customer and leave it available for the next. Four of the five causes are not technical, they are daily habits: recording later, promising without writing, not separating sizes. The first fix is behavioural before it is software. ## Step 1: make the unit the smallest thing you sell Do not record "blue shirt: 20". Record "blue shirt M", "blue shirt L", and "blue shirt XL" as separate units. The same rule applies to color, to any option with a different price, and to packaging sold in different sizes. The unit is not the product, it is the version the customer asks for by name. The practical test: if the customer might say "I want another size" after you sell to them, that needs its own line. If the size or color changes the price the reason doubles, because you are wrong about the quantity and the money at once. Watch out for sets and bundles. A two piece set consumes two pieces of its component stock. If you sell the piece separately and the set together, every set sale must deduct from each component, otherwise you reach a set you cannot assemble while thinking its parts are there. ## Step 2: one shared number across every channel If you sell from WhatsApp, from the cashier in the shop, and from an online page, every channel must see the same quantity. When you copy numbers by hand between places, the oldest copy does the selling, and it does not know what happened elsewhere. - Choose one place as the source, and every other place reads from it instead of editing it. - If manual copying is unavoidable today, give it one fixed time and write the last update time next to the number. - Stop selling from the channel that cannot see the number, or give it a known, limited quantity that is not mixed with the rest. A useful temporary fix: allocate an explicit quantity per channel. For example, hold four pieces for a live session or market stall and remove them from general availability first. Not full accuracy, but it prevents the surprise because the pieces were not sold twice. ## Step 3: deduct at agreement, not at delivery The moment the customer says "agreed" or "confirmed" is the moment to hold it, not the moment of shipping. If you wait until delivery another customer may buy that piece in between, and either way you promised two people one thing. Deduct at agreement right away, even if payment happens on delivery. 1. Confirm the order in one written line: product, option, quantity, final price. 2. Deduct the quantity from the right unit in the record in the same minute. 3. Write that the order is "reserved", not "delivered", they mean different things. 4. If the customer cancels, return the quantity with a recorded adjustment and a clear reason, not a silent increase of the number. 5. If unconfirmed after two days, ask one question before keeping the hold. Set a hold duration: a day, two days, or depending on the item. An open ended hold freezes stock nobody may buy, so the item looks available while it is held for a silent customer. Write the duration and return the quantity after it if no reply arrives. ## Step 4: a reorder point for each fast item The reorder point is the number at which quantity triggers an order, not the number at which you run out. The calculation is simple: how much you sell per day, multiplied by the days the supplier takes, plus a small margin for days you sell more than usual. A hypothetical example: an item you sell three pieces of daily, and the supplier takes four days. You need twelve pieces to cover that period, so ordering starts at that number not after it, otherwise you reach zero before the shipment. Add a margin for two heavy days and it becomes fifteen or eighteen pieces. You do not need this calculation for every item. Start with your fastest movers, ten or fewer, because they cause most of the apologies. A slow item does not need a reorder point, it needs a decision: should you keep buying it at all? - Fast item: a written reorder point and a weekly check of the number. - Medium item: a check every two weeks, and an order as it nears the end. - Slow item: no reorder, but an offer to clear it before it piles up. ## Step 5: record only three movements, and on time Everything that happens to stock falls into three types: in from a supplier, out by sale, and an adjustment with a reason. There is no fourth type. If you keep to these three the number stays honest, and if you skip one it becomes an opinion rather than a fact. 1. In: record the shipment when it arrives, not when its invoice is paid. 2. Out: every sale deducts from its specific unit, not from a general line. 3. Adjustment: damaged, lost, returned, or a counting error, with a written reason in one line. 4. Review: compare the number with the physical count, and never fix a difference silently. Returns deserve special attention, because a piece comes back to stock in two different states: a sound piece returns as an available unit, and a used or damaged piece does not return at all. Mixing the two ends with selling a piece that is not fit, which is worse than apologizing for a stockout. ## A daily and weekly checklist The lists below are short on purpose. A long list does not get done, and a short one done daily beats a complete system on paper. - Every morning: review open orders and return held quantities whose period expired. - After every sale: deduct immediately from the right unit and record the customer name with the order. - Every evening: check that the number of recorded orders matches the orders actually closed. - Every week: physically count the fastest movers and compare with the record. - Every week: review reorder points and adjust them if the selling speed changed. - Every month: a full count, and a list of items that did not move for a month. ## Common mistakes and how to fix them - Relying on memory: write the number where you can see it before answering any availability question. - An exaggerated safety stock: holding a lot of everything freezes your capital. Keep a buffer for fast items only. - Adjusting the number retroactively: "I will deduct at the end of the day" means every answer before then may be wrong. - Not recording damage: the piece that broke is still in the record, so it shows as available and gets sold. - A verbal hold: a promise with no writing disappears in two hours, and the piece is sold to someone else. - Selling a bundle without deducting its parts: the parts show as available while you cannot assemble a set from them. - One number for all branches: the deduction does not travel, so you think a piece is in the second branch when it sold yesterday. - Ordering from the supplier at zero: ordering at zero means days with no sales for that item. ## If this happens, do this - If you discover a stockout after promising: tell the customer the same day, before payment or waiting. A late apology is worse than the stockout. - If you have the same product in another color or size: offer it first with a photo, and leave the decision to them. - If the item is coming from the supplier: give a specific date, not "soon", a date keeps the order alive. - If the customer already paid: a full refund or an alternative with their agreement, not a long wait with no options. - If the same item runs out twice: the problem is the reorder point, not luck. Raise the number. - If the gap between record and count is large and repeated: find one cause, an entry error, an unrecorded sale, or unwritten damage. - If you sell on a live stream: allocate a known quantity and remove it from general availability first. - If the customer cancels after a hold: return the quantity the same minute, a frozen number blocks a real sale. ## Ready messages for a stockout apology A good apology carries three elements: quick acknowledgement of the situation, at least two options, and a date if there is one. An apology with no option leaves the customer to find a solution alone, and they usually find it at another store. - Apology with an alternative: "The size you asked for is actually gone. I have the same color in a close size, and another color in the same size. Want photos?" - Apology with a date: "The piece sold out hours before your order. The new shipment arrives on such a day, and I can hold one for you with no payment. Would you like that?" - Apology with a refund: "Unfortunately the order cannot be completed, and that is my mistake. I am returning the full amount today, and if you want an available alternative I can prepare it right away." - Apology after a delay: "I learned late that the item was gone, and I am sorry I did not tell you earlier. Here are your options now, and if none fit I will refund immediately." Notice that each message gives a clear next step, and none promises something you do not have. Promising an unconfirmed date is the fastest way to turn one apology into a complaint. ## Where a tool like FIHRIST helps Everything above can be done with a notebook, a sheet, and one rule: deduct at agreement. That is the way we recommend starting, and it needs no system. When channels and orders multiply, manual combining gets tiring. In FIHRIST, sizes, colors, and options are recorded as separate stock units, each with its own price and quantity, and every order deducts the quantity sold from the specific option. The order is linked to the customer and the product, an item can be identified with a QR code, and item movement can be compared across two periods to see what moves fast and what piles up. The interface works in Arabic and English. No system prevents every human error. Someone who forgets to record will make mistakes in any tool, but keeping one number in one place removes the most common causes and makes the error appear the same day rather than when the customer arrives. ## Frequently asked questions ### What is the difference between quantity on hand and available quantity? On hand is everything you actually own, including what is reserved. Available is on hand minus reserved minus damaged, and it is the number you can promise a customer. The gap between the two causes most double selling, because the seller reads the first number and promises it to the second customer. ### When should I deduct stock, at order time or at delivery? At agreement, meaning the moment the customer confirms the product, option, and quantity. Waiting until delivery leaves room for another customer to buy the piece in between. Deduct at confirmation, record the order as reserved, close it at delivery, and return the quantity with a recorded adjustment if the customer cancels. ### How do I calculate a reorder point for a fast item? Multiply your average daily sales by the days your supplier takes, then add a small margin for busy days. If you sell three pieces a day and the supplier takes four days, you need twelve pieces to cover the period, and ordering starts at that number or slightly before it. Review the number weekly and adjust it if selling speed changes. ### What do I say to a customer whose item sold out after I promised it? Say it the same day and offer at least two options: a close size or color, a hold from the next shipment with a specific date, or a full refund. Do not say "soon" without a date, and do not send an apology with no next step. Quick acknowledgement protects trust better than trying to cover the mistake. ### Do I need a minimum level for every item in the store? No. Start with your fastest movers only, ten or fewer, because they cause most of the apologies. A slow item is not helped by a minimum level but by a decision: keep buying it or clear it with an offer. Too many levels become a long list nobody reviews, and an unreviewed list is worse than none because it gives false confidence. --- # A checklist for taking orders on WhatsApp Source: https://fihrist.world/en/blog/whatsapp-order-taking-checklist Published: 2026-11-15 | Reading time: 8 min | Publisher: FIHRIST > Order mistakes rarely come from bad intent. They come from one unconfirmed detail: a size, a color, an address, or a price quoted without delivery. Here is a checklist to run through before closing every order, with worked examples and ready templates. ## Why orders fail on WhatsApp An order that fails on WhatsApp rarely fails because it is difficult. It fails because one detail stayed in one person's head. The customer understood delivery was free, you understood size L, the wrong item arrived, and the result is a return, a cut into your profit, and a bad feeling on both sides. Four patterns repeat more than any others: a voice note understood differently, a product photo without stating size or color, an address typed in a hurry with no landmark, and a price quoted before delivery was added. Each of these is cured by one item on the checklist below. The fix is not a special talent. It is one moment called confirmation: you gather everything you agreed on into a single message, send it to the customer, and wait for a clear reply before you touch stock or promise anything. ## The checklist before you confirm 1. Is the item actually in stock in the requested size, color, or option, not just the item in general? 2. Did you state the final price explicitly, including delivery or any other charge if it exists? 3. Is the requested quantity available, or is what remains less than the customer asked for? 4. Did you explain the exchange and return policy in one sentence, with no exaggeration and no extra promises? 5. Is the payment method clear and actually acceptable to you? 6. Is the delivery time you mentioned doable if another customer places the same order on the same day? 7. Do you know the customer's name and number, or are you talking to an account with no name? If there is one item you cannot answer with a clear yes, stop. At that moment the order is a draft, not an order. Ask the customer or check the stock, then continue. ## The details an order cannot close without - Full name, and a phone number that can actually be answered if WhatsApp goes quiet - Address with enough detail: street, building number, floor, and a landmark locals know - Size, color, or option written in words, not left as a picture - Quantity as a number, not a guess, because "a few" means something different to each person - Total amount and payment method, stating whether it is cash on delivery - The day or window when delivery is likely, phrased so you can keep it These fields are not paperwork. They are exactly what you need later when a customer asks where their order is. An order that does not record them becomes a memory after a week. ## The confirmation message: five parts and a ready template A good confirmation message is short but leaves no room for interpretation. Its order is the same every time: the item and its option, the quantity, the amount and payment method, delivery and address, then the policy and one closing question. - Item and option: prevents the most common error, arriving with a different size or color - Quantity: prevents the argument over "I ordered two" and "I understood one" - Amount and payment: prevents a surprise at delivery - Delivery and written address: makes correcting the address possible before shipping, not after - Policy and closing question: gives the customer a chance to object before goods move Template: "Order confirmation: blue cotton shirt, size M, quantity 2. Total [amount] including delivery, cash on delivery. Delivery to [street, building, floor, landmark], expected [day or window]. Exchange within [period] provided the item is unused. Are all the details correct?" Closing rule: do not treat an order as confirmed by a reply like "okay" alone when it contains more than one item or more than one detail. Ask for an explicit yes to the gathered message, because for some people "okay" means "I received your message". ## A full example, from first message to delivery 1. Customer: Hello, do you have the blue shirt? 2. Store: Hello, it is available in M and L. Would you like the available sizes in detail? 3. Customer: M, and I want two. 4. Store: Size M is available, the price is the listed one per piece, and delivery to your area is [amount]. Shall I reserve the two for you? 5. Customer: Yes, reserve them. 6. Store: Order confirmation: blue cotton shirt, size M, quantity 2. Total [amount] including delivery, cash on delivery. Delivery to [street, building, floor, landmark], expected [day or window]. Exchange within [period] provided the item is unused. Are all the details correct? 7. Customer: Correct, but the address is by the mosque. 8. Store: Noted, I added the landmark. The order is recorded and the size is reserved, and we will message you before dispatch. 9. Customer: Thanks. 10. Store: Thank you. If you need a size or address change before packing, tell me and I will update it. Notice what happened in that short conversation: the quantity was reserved from the right size, the address was confirmed before packing, and a follow-up point was set after delivery, all in a few minutes. Nothing new was bought and no special tool was used, only a fixed order to the conversation. ## Changes and cancellations: rules that protect both sides A change is not a problem. The problem is a change that arrives after the goods have left. So the best fix is to state clear time limits in the confirmation message itself, so the customer knows how long they can change their mind. - Before packing: change or cancellation is a fair right, change without argument and update the record - After packing but before dispatch: a change is possible if it has not left the shop; if it has, the answer is an exchange, not a change - After dispatch: no change to the order itself, but the customer may refuse delivery or exchange under the policy - Cancellation after dispatch: record the reason plainly, because repeated reasons reveal a problem in the description, the price, or the delivery An important record rule: do not erase the old order when it changes. Add a new version and keep the old one visible as cancelled or edited. In any later dispute, a sequential record settles the discussion in seconds, while an erased one reopens it. ## Special cases: cash on delivery, wrong address, and a stockout after agreement Cash on delivery: these orders carry more risk, because the customer may change their mind at the door. Reduce it with one confirmation before dispatch, a short message stating the exact amount due, and a record of each delivery attempt: delivered, refused, no answer. Someone who refuses twice in a row is not banned, but their third order gets an extra confirmation. Wrong address: do not rely on the map alone or on the district name. Ask for a fixed landmark locals know, a backup number, and a time when someone is at the address. If delivery fails, record the reason in the courier's own words: number not found, no answer, refused. That sentence is what lets you fix the description or choose a better courier next time. A stockout after agreement: this is the hardest moment, because the customer considered the matter closed. The right response is three steps: tell them immediately with no delay, offer three options rather than one (a close alternative, waiting with a specific date, or a full refund), and let them choose. Do not substitute the item on your own even if it is better, and do not wait until delivery day to explain. Customers forgive a stockout. They do not forgive a surprise on delivery day. ## Common mistakes and their fixes - Mistake: recording at the end of the day. Fix: record before you answer the next customer, because the order you remember two hours later is not the real order. - Mistake: relying on voice notes for orders. Fix: turn every order into text in the confirmation message, even if the customer prefers voice. - Mistake: quoting the price before delivery. Fix: always give the final figure, or say plainly "price before delivery". - Mistake: promising an optimistic delivery date to close the sale. Fix: give a window you can keep on a busy day, because a late promise costs more than early honesty. ## If this happens, do this - The customer does not reply to the confirmation: send one reminder after a reasonable gap; if there is still no reply, treat the order as unconfirmed and return the quantity to stock after telling them you did. - The customer only said "okay": ask one closed question, "shall I confirm the order with the details above?" so two readings cannot survive. - The customer changes the size after packing: do it if the item has not left, and if it has, explain the exchange option in one sentence without a long apology. - The customer says the price is different from what they saw: do not argue. Send what you have on record, say you will check, then correct the description or price after the call. - The courier says the customer refused delivery: call the customer before deciding anything and record what they say, because courier and customer tell two stories worth hearing. - The customer complains of a missing or damaged item: ask for a photo and propose one clear remedy (exchange, discount, or refund) instead of opening many options for yourself. ## Ready to copy templates - Confirmation: "Order confirmation: [item and option], quantity [qty]. Total [amount] including delivery, payment [method]. Delivery to [full address], expected [window]. Exchange within [period] if unused. Are the details correct?" - Change: "Your order has been updated. New version: [details]. The previous version is cancelled. Please check it and tell me if anything is wrong." - Cancellation: "The order is cancelled and the quantity is back in stock. Nothing is owed on your side. If you want to order later, I am here." - Stockout after agreement: "Unfortunate news: [item] ran out after your order was reserved. You have three options: [alternative], waiting until [date], or a full refund. Which suits you?" - Before delivery: "Your order is out for delivery today. Amount due on delivery [amount]. The courier will call [number]. If the address changed, tell me now." - After delivery: "I hope you are happy with the order. If there is any issue with the size or the item, tell me and we will find a solution." ## Three numbers to watch every week You do not need a complex report to discover that your order taking needs tuning. Three simple numbers are enough at the start, and you count them from your own record, not from memory. 1. The share of orders that reached the customer right the first time. Every returned order means a detail was never confirmed. 2. The number of orders cancelled or apologized for after confirmation, with each reason. The same reason repeating is the real news. 3. The number of conversations that ended with no reply from you or a late one. These are the fastest sales to lose. ## How FIHRIST helps Everything above runs on a notebook, a sheet, and a little discipline, and you do not need a tool to start. When conversations multiply, linking things by hand gets tiring. FIHRIST brings WhatsApp, Messenger, Instagram, email, and web chat into one inbox; each conversation links to the customer, product, and order; each conversation can have an owner and a status; and follow-up reminders can be switched off. Stock is recorded as units for sizes, colors, and options, each unit with its own price and quantity, and each order deducts the quantity sold. You can also print a QR code to identify items. The interface runs in a browser, in Arabic and English. ## Frequently asked questions ### Should I send a confirmation message for every order, even a small one? Yes, for a practical reason: the smallest orders are the ones closed fastest in the fewest words, and also the ones where a size or address gets forgotten. The confirmation need not be long, two lines are enough for a single item. What matters is that it goes out before you touch stock, because that is the only moment when correcting it is still cheap. ### How do I handle a customer who refuses to type and only sends voice notes? Listen to it fully, then write the summary yourself instead of asking them to type. Send the confirmation and add a line such as "I wrote your order down so we can confirm it". That way the customer keeps what they prefer and you get a written record to return to. A voice note is an interpretation; the text is what gets executed. ### What should I do if the item runs out after I confirmed the order? Tell them the same day if you can, and offer three options: a close alternative, waiting with a specific date, or a full refund. Do not choose for them and do not postpone the news to delivery day. If they paid in advance, start the refund before they ask, which turns a bad moment into one they remember in your favour. ### Should I ask for a payment transfer screenshot before packing the order? Ask for confirmation, but do not let a screenshot be your only proof. Better to check your own account or wallet, since images can be old or look alike. Make the rule fixed and stated: "we start packing once the amount arrives". A clear rule spares you embarrassment with a customer who forgot or was late. ### How do I reduce returns specifically for clothing? Add one sizing fact to the confirmation, such as a measurement in centimetres or a note that the cut runs small. One photo on a real body beats ten flat ones. And record the reason for every exchange: too small, too big, different color. After enough orders you will have a size guide built from your customers' notes rather than your guesses. --- # Is an AI assistant right for your store replies? Source: https://fihrist.world/en/blog/ai-assistant-for-store-customer-replies Published: 2026-11-15 | Reading time: 9 min | Publisher: FIHRIST > An AI assistant is not a replacement for your team. It is a layer that answers repeated questions and leaves decisions to you. This is a practical guide to what you automate, what you leave to a person, how to start safely, and how to correct it when it is wrong. ## What an assistant does and does not do The most common confusion is a store owner expecting a full employee, then feeling let down. An assistant that works from your store data is not a salesperson and not a negotiator. It is a first layer that answers questions whose answers you have on record, and leaves everything else to a person who knows the store. - It does: answer with a listed price, availability, options, opening hours, and a written policy - It does: reply when nobody is around, instead of leaving the customer waiting for hours - It does not: decide a discount, approve an exception, or promise a date you have not set - It does not: know what is not recorded. If your data is stale, its answer is just as stale - It does not: sense anger in a message, or know this is the third time this customer has complained ## Questions that are safe to automate A safe question has one correct answer that exists in your data, and a mistake in it costs little. Start with this group, because it gives the team time without meaningful risk. 1. The listed price of a specific item, provided the price in your data is the real price 2. Whether an item exists in a given size or color, if stock is kept in units and not as a general number 3. Opening hours, address, and contact method 4. The exchange and return policy exactly as written, with no improvisation and no exceptions 5. Available payment methods and whether cash on delivery is offered 6. The stated delivery time as a window, never as a promise of a specific date ## Risky questions that need a person - Complaints: "the order came late" or "the item is damaged". An assistant may argue or apologize in a way that fuels anger - Exceptions: "can I return it after the period?" That is an owner's decision, not a rule - Negotiation: any request for a discount, a bundle price, or a free item - Individual cases: a missing order, a transfer that did not show up, an unavailable size where they want a dated alternative - Questions you never recorded: "will the fabric survive washing?" If the fact is not documented, do not let it be invented - Any conversation containing anger, a threat to leave, or a mention of a past bad experience A practical rule of thumb: if the answer would be the same for any customer, it is a candidate for automation. If it depends on this particular customer or on your judgment, it belongs to a team member. The rule is not perfect, but it prevents most costly mistakes. ## Before switching on: prepare your store data The assistant mirrors your data, so there is no way to make it more accurate than your shelf. Fix the data first, otherwise you will deliver old errors to customers faster and in a more confident tone, which is worse than not replying at all. - Prices: one item with two prices in two places is the first thing to settle - Options: each size and color gets its own unit, price, and quantity, not one total for the item - Policies: write exchange, return, and delivery as short sentences that can be quoted word for word - Discontinued items: delete them or mark them clearly as unavailable, so the assistant does not answer about them confidently - Common questions: collect the last fifty real questions from your chats and write an approved answer for each ## A four week safe rollout plan Do not switch the assistant on across all conversations in one day. Week one is not about the assistant at all, it is about your data. Going step by step gives you a chance to catch an error before a customer does. 1. Week one, cleaning only: fix prices, options, and policies, and write twenty approved answers. Turn nothing on yet. 2. Week two, price and availability only: the assistant handles just this group, and you review every conversation at the end of the day. 3. Week three, peak hours: let it reply during busy hours or outside opening hours, while sensitive conversations stay with the team. 4. Week four, measurement: compare how many questions ended unanswered before and after, and how many answers the team had to correct. The decision at the end of the month is not "did I like it?" but "did fewer questions go unanswered, and did the answers stay correct?" If the answer is no, the problem lies in the data or in how narrowly you enabled it, not in the idea itself. ## When it should hand over to a person The real value of an assistant shows in how fast it hands over, not in how much it answers. An assistant that answers everything and never hands over is more dangerous than one that says "I will ask the store owner and get back to you" at the right moment. - On any complaint or mention of late, damaged, or wrong - On a request for a discount, an exception, or a delivery date pinned to a day - On a question with no answer in the data, however simple it looks - On any sign that the customer bought before and has history with the store - On a request to speak to a person, with no attempt to keep them with the assistant The handover should carry context: who the customer is, what they asked, what was already answered, and who picked it up. A handover without context forces the customer to repeat themselves, which is worse than waiting a little longer. ## How to audit the answers Auditing is not reading everything forever. It is a structured sample at the start, then a smaller sample as confidence grows. The goal is not to prove the assistant is good, but to find the error before a customer does. - First week sample: every conversation, with no exceptions, because volume is small and errors are likely - Afterwards: ten conversations a week, from different days and different question types - Record three fields per audit: the question, the answer, and correct, wrong, or incomplete - Any error repeating twice must become a change in the data or in the allowed question scope - Also review conversations that ended in silence, that is where unnoticed errors hide An example of a simple audit sheet: date, question in brief, what the assistant answered, the verdict, and what you did. After a month you will have a list of recurring errors, which is worth more than any general impression. ## What to do when the answer was wrong An error is not the end of the experiment, but how you handle it decides whether the customer stays. The order that matters: correct it with the customer first, then fix the cause, then switch the assistant off if the cause is still unclear. An example: a customer asked the price of a bag, and the assistant quoted the old price because the price had been changed in the shop but not updated in the data it reads from. 1. Correct it with the customer: "The correct price is [price], and I apologize for the confusion. Would you like me to complete the order at the correct price?" with no long explanation. 2. Fix the cause: update the price in the data, and check other items whose price changed in the same period. 3. Review the scope: if the error came from a question type the assistant should not answer, block it from that type instead of relying on its attention. 4. Log the incident: item, question, answer, correction. A second occurrence means a decision, not bad luck. And do not hide the error from the customer or excuse it with "the system said so". The customer dealt with your store, not your system, and a short clear apology costs less than an argument. ## Common mistakes when rolling it out - Switching on before cleaning the data: the fastest way to spread old errors in a confident tone - Enabling it on every question on day one: it hides where an error came from when one appears - Leaving it with no handover path: an angry customer in a closed loop leaves quietly - Not telling the customer a reply is automated: honesty sets the right expectation and makes a team takeover normal - Judging the experiment from one conversation: a decision this size needs at least two weeks and one number to compare - Relying on it for sensitive follow-up: whoever complained or asked for a refund needs a human name to deal with ## If this happens, do this - The assistant quoted a wrong price: correct it with the customer in the same conversation, then update the data, then find every item whose price changed recently. - The assistant promised a delivery date: send one clear correction, and block that question type until you write fixed windows. - The customer wrote "I want to talk to someone": hand over immediately with no questions, and pass the conversation context to whoever takes it. - The customer did not realize the reply was automated and asked for something impossible: apologize in one sentence, say who will follow up, and do not make them explain twice. - The same error repeated on one item: remove that item from the assistant's scope instead of switching everything off or letting the error continue. - The assistant stopped or failed: do not leave conversations open. Turn it off and send a short message to waiting customers that replies will be delayed. ## The analysis assistant is a different question Besides the customer assistant there is another kind: one that reads your store numbers and explains them. This kind is useful even if you never enable the first, because it does not talk to customers, it talks to you. The risk here is different: not a wrong answer to a customer, but a wrong conclusion you build a decision on. So always ask it for three things: the figure it relies on, the period it compared, and what the data cannot say. If it says "sales fell because a competitor cut prices", ask which of your own data proves that. If none exists, the cause is unknown, and that is a valid answer too. The general rule for both kinds is the same: keep the decision with you. A tool speeds up reading and replying, but it does not know the store, its history with a particular customer, or the consequences of a decision. ## How FIHRIST helps In FIHRIST, a unified inbox brings together WhatsApp, Messenger, Instagram, email, and web chat; each conversation links to the customer, product, and order; each can have an owner and a status; and follow-up reminders can be switched off. Stock is recorded as units for sizes, colors, and options, each unit with its own price and quantity, each order deducts the quantity sold, and you can print a QR code to identify items and compare item movement across periods. Permissions are set per member. The customer assistant answers from recorded store data only when enabled, you can keep it off and follow up manually, and your team can follow any conversation and step in, with the reminder that any AI can make mistakes. The analysis assistant explains only what the data supports. The interface runs in a browser, in Arabic and English. ## Frequently asked questions ### Can an assistant answer price questions without errors? It can be very accurate if the price in your store data is always the real price. Errors usually come from two sources: a price that changed and was not updated, or an item priced in two places. So the practical rule is to update prices in one place and recheck after any change. There is no full guarantee, which is why human takeover stays available. ### How do I tell a customer the reply is automated without losing them? One sentence in the first reply is enough, such as "I am the store assistant, and I can connect you to a team member at any time". What matters is honesty and an easy door out to a person. In practice, honesty reduces anger when an error happens, because the customer expects someone to follow up. ### What is the minimum data needed to start? You do not need everything, but you need at least three things: item names with their options, their real prices, and the exchange and delivery policy written down. Start with the twenty most asked about items and four common questions. A small trial on a narrow scope gives you a clearer signal than waiting for complete data. ### Does an assistant help a small store with no team? It helps more in that case, provided its scope is narrow. A one person store loses many questions because the owner is asleep or busy, and an assistant covers that gap if it returns decisions to the owner. If it is left to cover everything with no review, it multiplies the risk rather than reducing it. ### What if the assistant keeps giving a long apology in every conversation? That usually means the instructions it works from are too broad, so it tries to cover every possibility. Set the style with short limits: one apology sentence, then one practical step, then let the customer continue. Review ten conversations afterwards to confirm the length is no longer a problem. --- # How to choose a POS system for a small shop Source: https://fihrist.world/en/blog/pos-for-small-shops-what-to-look-for Published: 2026-11-15 | Reading time: 9 min | Publisher: FIHRIST > A good POS does more than record a sale: it tells you what is left and who bought. These criteria help you compare options without being swayed by a long feature list, and they protect you from a decision you regret a month later. ## Start from your normal day, not the feature list Before you open any offer, sit for ten minutes and write down what actually happens in the shop: who opens, who sells, how the price is set, how the sale is recorded, how you know what is left, and what happens when a customer returns an item. This page matters more than any comparison, because a system that does not match your day gets abandoned within a week and everyone goes back to the notebook. What shop owners complain about most is not missing features, it is a system that asks them to change how they work entirely. A good system fits into your day as it is and removes steps instead of adding them. At every screen ask: did this step exist before? If it is new, what does it save me? ## A quick evaluation checklist before any comparison - Recording a sale in few steps: pick the item, the quantity, the payment. Every extra step means a queue and a sale that may be dropped. - An immediate deduction from the right unit, meaning size, color, and option, because one total per product hides that a single size ran out. - Finding a product by name, code, or a scan, so selling does not depend on the team memorizing item names. - Tying the sale to a customer, even with an optional phone number, because that is what makes follow-up possible later. - Clear permissions: who sells, who edits a price, who deletes, who sees reports and cost. - Discounts and returns recorded with a reason, so you know what you really sell and how much leaks through discounting. - A daily close that comes out in one action and matches the cash in the drawer. - Data export to a spreadsheet file, because you do not want your numbers trapped inside a tool. - Working through an internet outage, or at least not stopping sales completely. - A clean Arabic and English interface your team understands from day one without long training. ## Speed of recording a sale: test it yourself Stand at the device before buying and record ten different items: one with a size, one with a discount, one for a registered customer, and one return. Time it yourself. If a normal sale takes more than a minute, the team will bypass the system when it gets busy, and that is not weakness on their part but the natural result of a queue waiting. Speed is not a luxury. At busy times, every extra second means a customer walking out or a wrong price. Slow systems do not force the team to be patient, they push them toward the paper that gets forgotten on the shelf. ## Linking the POS to stock: the most important technical question Ask directly: does a sale deduct from the unit or from the product? If an item comes in three sizes and two colors, you are selling six different units, and a single deduction from one total never tells you which size ran out. When you do not know that, you promise a customer something you do not have or reorder something you already have. Also ask about edge cases: what happens if two people sell the last available piece in the same minute? What if an item comes back, does it return to the same unit automatically or need a manual adjustment? Can you enter arriving stock quickly without walking through every screen? These cases are what eat your time every week. ## The sale and the customer in one place A POS that does not know who bought is only an accurate cash box. When the sale appears on the customer record, you know who buys every month and who stopped, and you can offer someone who bought a certain size what is available in it now. This does not need complex technology, it needs the customer to be part of the sale rather than a field always left empty. If your shop does not ask for a customer number at checkout, start with one optional question and explain the benefit calmly: being told when something is back or when a size arrives. Whoever declines is fine, and whoever accepts gives you a real link between the sale and the customer. ## Permissions: who sees what and who does what Write three roles before you choose a system: seller, supervisor, owner. The seller records, prints, and checks stock. The supervisor edits, accepts a return, and opens a shift. The owner sees cost and reports and changes prices. Then ask the vendor: does your system allow this split? Some systems give you one account for everyone, and then any employee can delete the whole day of sales with no trace. Good permissions protect the employee too, not only the owner. When deletion and editing are recorded under the name of whoever did it, nobody accuses anyone of a mistake, and the discussion becomes about the cause instead of the person. ## Returns and discounts: rules written in advance The first rule: every return and every discount gets a recorded reason. Not to hold the team accountable, but to know your real numbers. If a large part of your sales comes after a discount, you are not selling at the price shown at the top of the report, and your next decision must be built on the effective price. Returns repeat for three reasons: a size that does not fit, an unclear description, or a defective item. Each cause needs a different fix. The first needs a size chart and photos that show the measurement, the second needs a more precise description and realistic expectations, and the third needs the supplier themselves reviewed. If you merge the reasons into one number, you will fix the wrong one. Ask the system to require approval for a discount above a limit you set, and to link a return to its original order rather than creating a negative movement with no origin. Write your return policy where the customer sees it before buying, that reduces the argument at the door. ## A five minute daily closing routine Do not just collect the cash and leave the drawer. A short daily close prevents the pile up of errors that become impossible to explain a month later: 1. Count the cash actually in the drawer, not what you remember. 2. Compare with the cash sales total in the system and log any difference, however small, with a note. 3. Review incomplete or pending sales and close them before they are forgotten. 4. Check the returns recorded today and their reasons, not only their value. 5. Look at the items that hit their minimum level and leave a purchase note. 6. Write one line: what was unusual today? A promotion, a fault, an absent employee, an item that ran out. ## Ten questions to ask any system vendor - What happens to my data if I stop paying or close the account? Can I take all of it? - Can I export all sales, items, and customers to a spreadsheet in one action? - How are prices managed: one price per item or a different price per channel or per list? - Can a completed sale be edited? Who is allowed? Is there a record of the edit? - How does it handle sizes, colors, and options: separate units each with its own price and quantity, or one number per product? - What happens to a return after a week or a month? How is it linked to the original order? - Does it run on the device I already have, and what are the internet and printer requirements? - How is training handled? Is there Arabic support during my working hours? - Where is the data stored, who owns it, and what is the backup policy? - What are the cancellation and migration terms? What is charged extra later? ## Red flags to stop at - A trial that cannot import your items, forcing you to enter the whole shop by hand before seeing any benefit. - The system asks you to change how you work entirely, rather than the other way around. - No data export, or an export that is only an image. - No permissions, or one account everyone shares. - Stock as one total per product with no sizes or colors. - No record of what was edited or deleted, so you cannot tell who changed what. - Open promises about something you need today: we will add it soon. Ask for a date or treat it as absent. - Support does not speak your team language, so problems arrive after employees have learned to work around it. ## A one week trial plan A real trial is not a demo session in front of the vendor, it is a week of your own sales. Run it in this order: 1. Choose a normal week, not a big promotion week and not a holiday week. 2. Load only your best selling items, twenty to thirty of them, not the whole shop. 3. Run the system in parallel with your old method and record every sale in both. 4. At the end of each day compare three numbers: total sales, order count, and items that ran out. 5. Ask the person who actually stood at the device, not the one who sold you the system. 6. On day seven write three points: what it saved, what slowed you down, what is missing. 7. Decide clearly: adopt it, extend the trial a week, or leave it. Do not sign a long commitment before this step. If the team avoids the device in the first week, the problem is usually speed or training, not the team. Write down what they tell you word for word, it is the most honest review of the system you will read. ## Where FIHRIST stands against this list The POS in FIHRIST runs in the browser on the same products and stock, so a sale deducts from the specific unit and shows on the customer record. Each size, color, or option is its own unit with its own price and quantity, a QR code can be used to identify an item, an order can be linked to the conversation it started from, and item movement can be compared across periods. Permissions are set per member, and the interface works in Arabic and English. Contact us about suitable devices or multiple branches. Start with the checklist and the one week plan above, they work with any system you choose. ## Frequently asked questions ### Does a very small shop need a POS system? You do not need a system just because you sell, you need one when the numbers exceed what you can remember: items with several sizes, sales over more than one channel, and one or two employees. If you sell ten pieces a day and know what is left, a notebook is enough for now. The trouble starts when you promise a customer something that ran out, or discover a week later that profit was not what you assumed. The decision depends on the volume of work, not the size of the shop. ### What is the difference between a POS and an inventory system? The POS is the point of sale: the screen where the sale is recorded, the receipt printed, and the money collected. An inventory system tracks quantities, units, minimum levels, and movement history. When they are separate, you record the sale in one place and deduct in another by hand, which is the source of most conflicting numbers in small shops. It is better for sales and stock to sit on the same data, otherwise you spend time reconciling every week. ### Can a POS run on a phone or an ordinary laptop? Many modern systems run in a browser, meaning from a laptop, tablet, or phone, without installing heavy software. Before buying, ask three things: does it need a permanent internet connection, does it work with the printer you have, and is a small screen enough to browse items quickly. Test on your own device, not the demo device, because speed on your device is what decides whether the team will use it. ### How do I weigh the cost of a system against a notebook? Do not compare the subscription price with the price of a notebook, compare it with what you lose today: a sale dropped because of a queue, an item that ran out unnoticed, a discount given and never recorded, an old customer who did not come back. Write three estimated numbers from your own week, then decide whether the system fixes at least one of them. Always ask what is charged extra later, and start with the smallest plan that covers your current work. ### What do I do if the internet drops during selling? Ask about this before buying and write the answer down. Some systems keep working locally and sync when the connection returns, others stop. If your system needs internet, keep a simple paper fallback: item, quantity, price, time, then enter those when you are back and record them as adjustments so stock stays correct. What matters most is that the team does not start selling without recording, because that gap shows up days later and is hard to trace. --- # Sales report basics for store owners Source: https://fihrist.world/en/blog/sales-report-basics-for-store-owners Published: 2026-11-15 | Reading time: 8 min | Publisher: FIHRIST > A report is not a goal, it is a tool for a decision. These simple questions turn numbers into something you do this week, and protect you from a quick conclusion that costs you a month. ## A report answers only three questions What tires a store owner most is opening a report with twenty numbers and not knowing where to start. Simplify: what sold? What did not sell? And are the numbers better or worse than a similar period? Everything after that is detail serving these three questions, and whatever does not serve them can be ignored this week. The common mistake is reading the biggest number on the page as a verdict. Total sales can rise while profit falls, and can fall while the shop is in better shape. That is why you need two or three numbers together, not one, before judging. ## The metrics a small store actually needs, and how each is calculated You do not need twenty indicators. This set is enough for a weekly decision, and each one can be calculated from a simple export or by hand at the end of the day: - Order count: count confirmed orders only, not conversations. A chat is not an order until a product, a price, and a delivery method are agreed. - Total sales: the sum of order values after discount. If you separate shipping, keep it outside the figure or show it separately, so revenue does not look bigger than it is. - Average order value = total sales divided by number of orders. It tells you whether a customer is buying more or less per visit. - Units per order = units sold divided by number of orders. Useful if you sell small pieces, because it reveals multi item buying that an average price hides. - Conversion rate = orders divided by new conversations, multiplied by 100. It measures how well a conversation reaches a decision, not message volume. - Gross margin per item = (selling price minus purchase cost) divided by selling price, multiplied by 100. Calculate it per item, then look at each item weight in sales, because the best seller may not be the most profitable. - Return rate = returned orders divided by delivered orders, multiplied by 100. Divide by delivered, not confirmed, because an order that has not arrived cannot be returned. - Item turnover = units sold in the period divided by the average units held in stock during the period. A higher figure means stock is moving, a lower one means capital sitting on the shelf. - Average daily sales = period sales divided by actual selling days, not the number of days in the week. This single figure saves you from unfair comparisons. ## A weekly review routine in half an hour A review that happens every day gets read and not acted on. Set a fixed appointment, once a week, ideally the same day and hour, and follow the same order each time so you do not skip a step: 1. Write the nine figures above into one sheet or file, in the same order every week. 2. Compare with last week, then with the same week last month if you have it. 3. List the top five and bottom five items by movement, and add a reason if you know one. 4. Review items that ran out or hit their minimum, they explain part of any drop. 5. Review returns with their reasons, and conversations that went unanswered. 6. Choose one decision for next week and write it in measurable terms: what you will do, and on which item. 7. Write one line about circumstances: a promotion, a holiday, a supplier pause, a fault. A month later this line is the difference between an explanation and a guess. ## A worked example: reading two consecutive weeks The figures below are entirely hypothetical, for illustration only, and the currency unit is unspecified because what matters is the relation between the numbers, not their size. We also assume every order was delivered in both weeks, so the return rate is calculated on one basis. - Week one: 200 new conversations, 40 orders, sales of 12,000, 56 units sold, 4 returns. - Week two: 260 new conversations, 44 orders, sales of 12,100, 66 units sold, 3 returns. On a quick look, sales are almost flat: from 12,000 to 12,100. But the arithmetic says something else. Average order value fell from 300 (12,000 divided by 40) to 275 (12,100 divided by 44). Units per order rose from 1.4 (56 divided by 40) to 1.5 (66 divided by 44). Conversion fell from 20 percent (40 divided by 200) to about 17 percent (44 divided by 260). The return rate improved from 10 percent to about 7 percent. The honest reading: the shop did not grow, it changed shape. Customers bought more pieces but cheaper ones, and the proof is that average unit price fell from about 214 (12,000 divided by 56) to about 183 (12,100 divided by 66). At the same time you needed more conversations to get each order. That leaves two possibilities until you check: either a cheap item drove the volume this week, or discounts increased. The difference matters: the first is a product mix shift, the second is less profit on the same revenue. How do you settle it? Open item movement for week two and see which item added the extra ten units. If the whole addition came from one cheap item, mix is the cause. If the increase is spread out with a higher discount share, discounting is the cause. In both cases write what you found next to the number, because next week will be compared with this one. ## Comparison traps: when two numbers cannot be compared Most wrong conclusions do not come from bad intent, they come from comparing two numbers that do not measure the same thing. These are the most common traps in a small shop: - Number of days: a week with a holiday or a closed day cannot be compared with a full week. Use average daily sales instead of the total. - Season: the last week before a holiday or during Ramadan is not a normal week. Compare with the same month last year if you have it, or accept that the comparison is weak and write that down. - Stockouts: if a fast mover was out for three days, its lower figure is not weaker demand but absent supply. Exclude the days it was missing. - A price or discount change: higher sales after a big discount may mean lower profit. Compare revenue and margin together, not revenue alone. - One large order: a customer buying a batch once distorts the average. Note unusual orders in the margin of the report instead of letting them create a rule. - A change in how you measure: if you only started recording conversations this week, conversion cannot be compared with any earlier week. Start measuring and treat the first week as a baseline. - A channel shift: conversations moving from WhatsApp to Instagram does not mean WhatsApp declined, it means people changed place. Look at the total before judging a channel. ## When a higher number is bad news Not every rise is a success. Four cases deserve a review before celebrating: sales up with returns up, because you are selling what comes back; sales up with margin down, because you are buying volume at the cost of profit; order count up with average value falling sharply, because you get more effort for the same revenue; and conversations up with orders flat, because you pay in reply time with no result. ## From observation to decision: if this, then that - If sales rose and average order value fell: check the discount share and the item mix before calling the month a success. - If conversations rose and conversion fell: check reply speed and the most repeated question, one question may be blocking the decision. - If sales fell and returns fell with them: the drop may come from a narrower assortment rather than weaker demand. - If one item fell while a substitute rose: that is a shift inside the shop, not a loss. - If one item keeps appearing in returns: check the description, sizes, and photos before you stop buying it. - If a fast mover hits its minimum twice in a month: raise the minimum level or shorten the supply lead time. - If an item sells slowly but has a high margin: do not drop it immediately, try offering it to whoever bought something close to it. - If an item sells fast with a thin margin: revisit the purchase cost or raise the price slightly and measure the effect for a week. - If the gap between drawer cash and the report repeats: review the closing routine and permissions before suspecting a person. ## Common mistakes in reading reports - Changing several things in one week then trying to find out which one worked. Change one thing and read its effect. - Judging from a single day. One day may be a holiday, a fault, or a mood, and a week is the smallest unit worth reading. - Comparing this month with last month without looking at day count or holidays. - Reading revenue only and ignoring margin, so you believe you profited while standing still. - Not writing down what happened. Three weeks later you will not remember the supplier delay or the stockout, and you will explain the number wrongly. - Using the report to judge the team instead of improving the work. Numbers point at a step that needs adjusting, not a person to blame. ## What to write each week so comparison becomes possible The most important thing about a report is not what it shows today but what you keep for comparison tomorrow. Keep one page per week with the nine figures, the top items and the bottom items, one reason for each unusual movement, and one decision you made. After two months these pages become a series, and they are worth more than any ready made report because they carry your own explanation. If you do not have time for all of this, keep only three numbers each week: total sales, order count, and the fastest moving item. Three numbers written regularly beat twenty numbers forgotten. ## Where FIHRIST helps All of the above can be done with a spreadsheet, paper, and a pen. What FIHRIST offers here is specific: an analysis assistant that compares periods, product movement, and channel results, and explains only what the data supports, and you can always check the numbers themselves. Comparing item movement across periods helps you see what moved and what stalled, permissions are set per member, and the interface works in Arabic and English. The decisions remain yours. ## Frequently asked questions ### How often should I review the sales report? Once a week is enough for most small stores, on a fixed day and hour, because a week is the smallest period that gives a meaningful figure. A long daily review gets read and not acted on, but a short daily close is necessary for the numbers to be sound. The monthly review is for direction, assortment, and margin, not for tracking every order. ### What is the most important number in a sales report? No single number is more important than the rest, but if you must pick one it is gross profit rather than total sales. Revenue tells you the volume of activity, margin tells you what stays with you. A shop selling a lot at a thin margin works harder and earns less. So read revenue, margin, and order count together, those three reveal whether growth is real or just movement. ### How do I know whether a sales drop is seasonal? Compare with the same month last year if you have those figures, and see whether the drop happened at the same time. If you have no old figures, look for other signals: did the pattern repeat before or after a holiday, and did all items fall or only one. If one item fell while the rest held, the cause is probably that item rather than the season. When you are unsure, write cause unclear and watch for two weeks. ### Do I need accounting software to read a sales report? No, a sales report answers questions about selling and movement, while accounting belongs to tax, financial statements, and your statutory obligations. A small store can start with a spreadsheet holding sales, orders, items, and cost, and calculate the metrics in this guide from it. What matters is that the same data stays consistent, not that the software is complex. As the business grows, accounting becomes an organisational necessity rather than a condition for reading sales. ### Why does the sales figure in the report differ from the cash in the drawer? Because they measure two different things. The report measures the value of what was sold, the drawer holds what was actually collected. The gap usually comes from credit or online sales, collected shipping, a return paid in cash, and a change error or an unrecorded discount. Separate cash from non cash at closing, record every movement outside a sale, and the gap shrinks to something you can explain. ---