Taf9eel

Contents

1Who this is for, and why

The small shop today runs on a carbon-copy ticket, a ledger and the owner's memory. The recurring mistakes are well known: a ticket goes missing and the measurements are taken again; an argument over the date ("I said Thursday"); finished pieces hang on the rail for weeks because nobody told the customer; a fitting is forgotten and the bridal gown runs late; a cash drawer that does not match at the end of the day; and an Eid season in which the shop accepts more orders than the workshop can finish. At the end of the month the owner counts, from memory, the pieces each tailor completed.

Taf9eel addresses exactly these points, and keeps what the tailor already knows: the same collar and pocket drawings, the same order of measurements, the same ticket — but on the phone, with a memory that does not get lost. It serves the menswear tailor, the ladies' tailor, the suit maker, the shirt maker and the uniform workshop alike: the shop chooses its specialty, and its garments and their measurements appear. It does not see what it does not need.

2Every kind of tailoring: specialties and garments

During setup the shop chooses its specialty — one or several — and the garments are prepared with their measurements, illustrated options and printed measurement card. The specialty can be changed later from the garment library, all garments of a specialty can be added in one tap, or the shop can start from a blank garment and define the fields itself.

In total, 67 ready-made garments. Each has its measurements in inches with sensible ranges that warn but never block, its tailoring options, its default price, metres and lead time, and the tailor's piece rate. Everything can be edited in the field editor.

3Measurements and options by picture

This is the feature any tailor recognises at once, because it is taken from the paper order form used in Bahraini shops: columns of small drawings, a drawing of the garment in the middle, and boxes for the deposit, the balance and the total. Measurements are typed in inches with fractions, the way the tailor writes them on paper (40½ or 40 1/2), and when recording a piece the staff member taps the drawing they want instead of reading a text list; the chosen option is highlighted, and the value is stored under a fixed code so it does not change if the label is renamed later. Any option can carry an extra price (for example, embroidery +2.000), which is added to the piece price automatically.

The thobe

• 9 collar types: standard stand collar, angled tips, rounded tips, V opening, cut-away, round collarless, and shirt collar pointed / button-down / rounded.
• 8 pockets: none, square, rounded bottom, angled, with flap, pointed, round, hexagonal.
• 4 front plackets: full with visible buttons, pointed end, angled end, hidden buttons.
• 4 cuff types: square, angled, rounded, or no cuff.

Suits and trousers

• Lapels: notch, peak, shawl. Button stance: single-breasted with one, two or three buttons, and double-breasted with four or six. Back vent: none, centre, double. Pockets: flap, jetted, patch.
• Trousers: flat front, single pleat, double pleat; hem plain or with turn-up.

Shirts

• Seven collars: spread, classic, cutaway, button-down, club, band, and wing for the tuxedo. Cuffs: one button, two buttons, French, short sleeve. Plus the placket, the pocket, back pleats, and the monogram and its position.

Ladies' wear

• Necklines: round, V, boat, square, sweetheart, high, collared. Sleeves: sleeveless, cap, short, elbow, three-quarter, long, bell, puff. Dress silhouettes: A-line, straight, fitted, mermaid, ball gown, empire.
• Abaya cuts: closed, open, bisht, butterfly, kimono — with the embellishment and its placement, the closure and the sheila.

On screen: pictures, not paragraphs

• Wherever a piece's options used to read as a long line of "name: value", they show as their drawings with a short name under each: on the tailor's "My work" cards, on the order's pieces and on the pieces of a new order, where tapping a drawing changes that option. Only the options set differently from the garment's own defaults are written out, as short tags; every option is one tap away under All details, with the customer, the date, the fabric and the notes. This works for every kind of garment and in each person's language (field names in Hindi, Urdu or Bengali on "My work", option names in English as before).

The printed card (A4)

A card resembling the paper form is printed for each piece: order number, name and phone, date and collection date, the columns of drawings with a ✓ on the chosen one, then the matching garment drawing — thobe, kandura, bisht, sirwal, suit jacket, long coat, waistcoat, sherwani, trousers, shirt, kurta, dress, gown, blouse, lehenga, skirt or abaya — with the measurements written in inches in place with arrows, a fabric box, then the deposit, balance and total, payment methods and the tailor's notes.

4Customers and measurements

Measurements in inches

• Inches are the default, because that is what most Gulf tailors use, with centimetres available in Settings for a shop that prefers them. One unit everywhere: the measurement form, the customer file and version history, the workshop ticket, the illustrated measurement card and its figure, the cutting sheet, and Excel import.
• Fractions as on paper: staff type 40½, 40 1/2, 40.5 or even Arabic digits ٤٠ ١/٤, and the system shows measurements in the eighths every tailor knows (57⅛, 40¾). The usual range for each measurement and the "outside the usual range" warning appear in inches too, as do the limits in the garment editor.
• Nothing saved changes: measurements are stored internally at a fixed precision, so switching between inches and centimetres at any time only changes what is displayed and never touches a recorded measurement. Fabric stays in metres, because that is how it is bought and sold.

The customer file and measurement versions

• Customer file: name, phone, area and notes; tags (VIP, seasonal, late payer, prefers English, brings own fabric) with the option to add custom tags; and standing preferences shown in a highlighted colour while any order is being recorded ("likes the sleeve slightly longer").
• Versioned measurements: every new measurement is saved as a version (v1, v2…) with its date, who took it and its photos, and the difference between two versions is shown (chest 108 → 110). Each piece is linked to the version it was sewn from.
• Sanity warning: a value outside the usual range shows a warning without blocking the save. A value no garment has (zero or less, not a number, or more than twice the field's usual maximum and over 500 cm, so a bridal hem sweep of 1,200 cm still saves) is refused and its field is marked.
• Families and organisations: a father ordering for his sons, or a company ordering for dozens of employees. Individuals are added under one customer (with their relationship, and without a phone number where needed); each piece asks "who is this for?" and uses that person's measurements; one invoice goes to the payer. Pasting a list of names creates the individuals in one go.
• Merge duplicates: a customer recorded twice is merged in one tap, and the orders, invoices and measurements move to the correct file.
• Import: from Excel, CSV or phone contacts (vCard), with column mapping and a row preview before anything is inserted, including measurement columns on the garment you choose (thobe, abaya, suit, uniform…). The titles row is found even when it is not the first. One field takes one column: “Other phone” is the second number and never wipes the first, “Cuff height” is not the cuff, a column that looks like a field another column already has stays on “skip” and is named on screen, and picking a field for a column moves the column that had it back to “skip” in front of you. Opened from the Customers screen or from Settings; the owner's PIN is asked for at the end. An old invoice log (one row per visit) becomes one customer per person: rows with the same number and name merge, and for a number that carries several names the owner chooses one customer under the name they pick, separate customers (the person with the most rows keeps the number, the others get it as a second number) or skip, with a suggestion that merges only names that read as one. A number already in the shop fills in its customer's empty details and changes nothing else.
• Re-measure reminders: Today's "Needs you" list has a line for each customer whose last measurement is older than the set period (children 12 months, adults 24 months — both adjustable) with a WhatsApp reminder button, and a "measurement is old" warning appears when adding a piece for such a customer. School uniforms count as children's measurements.

5Orders

Recording an order

Three steps on the whole screen (no tab bar; a close button asks before dropping the order): customer (recent customers first, each with a «Repeat» button for their last order) → pieces (each piece is a card with its drawing, fabric, measurement and price; fabric from the shop by roll, metres and fabric price, or from the customer with the metres received and a description) → date and payment (date, rush, the total with VAT, deposit chips, the payment method; discount, notes, extra charges, accessories and quotation behind «Other options»). The ticket is printed or sent by WhatsApp on creation.

• Quick add: buttons with the garment names in the pieces step; one tap adds the piece with its price, the customer's usual options and their latest measurement, and the measurement form only opens if the customer has never been measured for that garment. The tailoring options arrive filled in "as usual for this customer" and stay visible for the staff member to review before saving.
• Straight from search: typing a name or phone shows a "＋ Order" button next to the customer, and if nobody matches, "New customer" appears with the name or number already filled in. The search ignores how an Arabic name was spelled (أ / ا, ة / ه, ى / ي, diacritics, "عبد الرحمن" / "عبدالرحمن"), so the same customer is found and not added twice.
• One-tap reorder from the customer page or from any previous order, with the piece options filled in "as usual for this customer".
• An accessory on the same invoice: in the pricing step a store product (ghutra, tie, sheila) is added as a line on the order and deducted from its stock.
• A date per piece within a single order (two thobes before Eid and three after), while the invoice stays one.
• Customer's own fabric: record the metres received and a description, get a warning if the metres are not enough for the number of pieces, and print bag tags (T-1023/1) to avoid the "this is not my fabric" dispute.
• Rush orders: a rush fee is added automatically, with a daily limit on rush orders; going over it needs the owner's PIN.
• Deposit policy: a minimum percentage, a higher one in season, and an option for the deposit to cover the fabric value; anything below policy needs the owner's PIN and is logged. At payment there are ready amount buttons: All, Half, 5, 10, 20, 50.
• Editing an open order: add a piece, cancel a piece that has not started (its fabric returns to stock) or change the date, and the invoice updates automatically; changing a price or the discount after invoicing, or cancelling a piece once a payment was taken, needs the owner's PIN, and the database refuses the same change from anywhere else; a piece added later is written to the activity log with its price. Cancelling or deleting an order returns its accessories to stock.
• Quotations: from the pricing step of a new order, "Save as quotation" keeps the pieces and prices and sends a quotation PDF on WhatsApp, valid for a set number of days (14 by default). The Quotations list shows open, expired, accepted and cancelled quotes; "Turn into an order" reopens the order at the quoted prices, and creating it marks the quote accepted with a link to its order. A quotation PDF sent again shows the figures it was saved with (total, VAT and its rate, each piece's fabric at the quoted price), even after the VAT rate or a fabric price has changed; the order made from it prices the shop's fabric at today's price, as any new order does.
• Quick service for alterations and hemming: one screen, no measurements, a named customer or a "walk-in", immediate payment, and a receipt that is printed or sent on WhatsApp.
• Paper ticket entry when moving to the system mid-season: the customer, number of pieces, agreed total, deposit and the ticket number exactly as it is on paper, so numbering continues from where the ledger stopped. A ticket number at or below one already used only brings a warning, and the order takes the next free number, in the cloud as in the demo.

6The workshop and fittings

• Orders: one card per open order with its number, customer, garments and cloth, how soon it is due (or how long it has waited, once ready), "at risk" when it may be late, and a progress bar to its stage; a search by number or name and one row of filters (all, late, today, ready, in the workshop) with their counts. A ready order's card shows its next step: tell the customer on WhatsApp, or what is still owed. The board, every order in a table with its filters (delivered and cancelled too, by tailor and dates), the calendar, the cutting list, collections, deliveries, quotations and paper tickets are one tap away under "Views".
• The board: columns received → cutting → stitching → (fitting) → finishing → ready → delivered. Each piece is a card with the order number, customer, date and tailor; drag and drop moves it between stages, and every card has a button named after the next stage ("Cutting ›", "Ready ›"). On a phone, a strip with the stage names and counts jumps to the column. Two devices cannot corrupt each other's edit (a version lock on every record).
• Cutting list: the waiting pieces grouped by roll, with the metres needed against the metres available; "Start cutting selected" assigns the cutter and moves the pieces together, and the cutting sheet prints the measurements of every piece in one table.
• Daily plan: an A5 page per tailor with their pieces ordered by date, to hang by the machine.
• The "My work" screen on the tailor's phone: only their pieces, with large "Done → next stage" buttons (a mistaken tap is taken back with Undo on the message that follows, or later with "Back to" the previous stage on the card), and an optional third language (Hindi / Urdu / Bengali) for the whole screen: stage names, garment and measurement names, the measurement sheet (with "—" for anything not measured) and the quality check. Anything not yet translated shows in English rather than Arabic.
• Urdu and Hindi across the app: every screen, button and message inside Taf9eel is also in Urdu (right to left) and Hindi, chosen from the language button or from each person's own language in Settings → staff, which the app switches to when they type their PIN and leaves when it locks. Counts agree with the number ("3 رسیدیں", "2 लोग"), dates use the language's month names with western digits, and Urdu uses the phone's own font so every letter joins. What reaches customers stays in the shop's language: WhatsApp messages, tickets, invoices, receipts and their PDFs are in Arabic and English whatever the screen shows. The Urdu and Hindi files load only for those who pick them, and then work offline.
• At risk: before an order is late, the system compares the days remaining with the stages not yet done (with adjustable days per stage) and raises a warning on the board, on the order's card and in Today's summary. A garment's own lead time sets the pace, so a two-day hem is not flagged the moment it is taken in.
• Daily capacity: when choosing a date, that day's load is shown against the workshop's capacity together with the "first available day", and a six-week calendar colours the days by load.
• Season calendar: the dates of Ramadan, Eid al-Fitr and Eid al-Adha are calculated on the Umm al-Qura calendar and suggested as seasons with a start, an end and a last day to accept orders; Today shows the countdown and the number of pieces due before Eid as one line, with the campaign a tap away, and an order after the last day needs the owner's PIN.
• Rework: a ready or delivered piece is sent back with a reason from a list (sleeve, collar, chest…); before delivery it returns to stitching, and after delivery a linked alteration order is created free of charge within a set period. Reworks are counted per piece.

The fitting stage (optional)

• Garments that need a try-on before finishing — suits, jackets, bridal and evening gowns, sherwanis, dresses — pass through a fitting stage between stitching and finishing. Thobes, shirts and the rest skip it automatically, and the fitting column only appears on the board for a shop that sews these garments. Each garment has a "needs fitting" switch in its settings.
• When a piece enters fitting, the date and time are set and a WhatsApp message opens inviting the customer. On Today, a fitting with no time set has a "Set a time" button, each of today's fittings a reminder button (in the order of their times), and a fitting whose day has passed is listed with the late work, with "Fitting done".
• After the fitting the required adjustments are written down, then the piece goes to finishing or back to stitching for a second fitting. The number of fittings and the notes of each are kept on the piece and in the timeline.
• The fitting has its own days in the date calculation and in the early lateness warning, and the customer sees it on the order tracking page.

Quality check before "ready"

• A piece only becomes "ready" after a checklist: measurements match the card, stitching and seams, buttons and zip, collar and sleeves symmetrical, hem, extras as ordered, no threads or marks, pressed and bagged. The list is editable in Settings, in Arabic and English.
• Everything ticked = "passed", and the piece moves to ready with the name of whoever checked it and an optional photo. Anything unticked = it goes back to finishing or stitching with the failed points and a note, and the piece carries a "failed QC" badge.
• The number of times a piece was sent back is counted on the piece and in tailor performance, and "a tailor cannot check his own piece" is there for shops that want a second pair of eyes. The check can be switched off entirely for a shop that does not need it.

7The customer and communication

• WhatsApp ticket at drop-off: order number, pieces, date, amount paid and balance. The message is the ticket the customer actually keeps.
• Ready notice and balance reminder with templates editable in Arabic and English, carrying the shop's BenefitPay number and IBAN and the rail location.
• Late order apology, after a look at the work: on Today, a late order is one line whose button opens its delivery plan: where each piece is, who has it, roughly how much work is left at the shop's pace, and so the date the shop can keep. Nothing is sent or changed by looking: from the plan (or the order's next step) the apology goes with that date (editable message) and can move the order's date at the same time; never a reminder about money.
• Notification log: the shop knows the customer was notified "3 days ago by Raju", finished pieces whose owner has not been told are shown, and there is a "second reminder".
• Automatic WhatsApp: the owner connects the shop's own WhatsApp Business number once (Meta's Cloud API), and Taf9eel then sends approved message templates by itself: when an order becomes ready, the day before a fitting, for ready orders not collected after a set number of days (then again at the same interval), and when a delivery goes out. Each kind can be switched off, the access token is kept where only the sending service can read it, and the customer's page has a Messages tab with every automatic message and its status beside the WhatsApp the staff sent by hand. To keep the shop's number in good standing, one number gets at most 10 messages a day, a shop sends at most 300 an hour, a delivery is announced once a day per order, a customer's name with a link or a phone number in it is not used as the greeting, and a shop whose subscription is locked sends nothing.
• Season campaign: a list of customers who ordered in the same season last year and have not ordered this year, with an early-booking message and a record of who was contacted.
• Marketing lists (Customers → Marketing lists): customers not back for a while (no order for 3, 6, 12 or 24 months, regulars first, filtered by tag) with a "we miss you" message; birthdays in the next 7 or 30 days with a greeting (the customer card keeps the day and month only, never the year); one occasion message (National Day with its date for the shop's country, Eid al-Fitr, Eid al-Adha, Ramadan, new fabrics or any other) to everyone who ordered in the last 12 months or to all customers, with the Arabic and English wording editable; and where customers come from (friend, Instagram, Snapchat, TikTok, Google, passing by, employer), asked on the customer card and counted for this year, the last 12 months or all time. Messages go one by one from the shop's WhatsApp in the shop's language, or in English to customers tagged "Prefers English"; each list shows who was already contacted, and the owner or a manager can copy the numbers. The shop's own wording of a message is kept on that device for that shop, and each demo keeps its own.
• Public tracking link: the customer opens it without logging in to see their pieces in plain stages (received, in progress, ready, delivered), their date, their balance in the shop's currency, a call button and the shop's address, and a thank-you once the order is delivered; it is printed on the ticket and added to the order-received WhatsApp message. The link stops answering 30 days after the order is delivered or cancelled.
• Collection: a rail location assigned automatically when ready, collection hours mentioned in the message, and an "awaiting collection" list split by age (under 7 days, over 7 / 14 / 30) with uncollected pieces flagged.
• Fitting invitation with the appointment, an "on the way" message when the driver sets off, and a re-measure reminder — all with templates editable in Arabic and English.
• Fabric book link: the customer browses the shop's fabrics and prices from their phone and asks by WhatsApp.

8Money

• VAT-inclusive prices: VAT (10% in Bahrain) is calculated once on the invoice total after discount, to the fils, and its rate is fixed on every invoice at creation; changing the setting later never touches old invoices, and a reprint keeps its own title, VAT lines and whether the shop's VAT number is on it (print and PDF). The printed invoice is a "Simplified Tax Invoice" with the required details. VAT is switched on only with the shop's VAT number (15 digits for a Bahrain shop; spaces are dropped) and a saved shop address, and Settings will not clear the address while VAT is on. An invoice also keeps the particulars it was issued with: the shop's names (Arabic and English), address and VAT number, and the customer's name, VAT number and address, so editing the customer or the shop later never rewrites an old invoice or turns a simplified one into a full one, and a renamed shop's old invoices keep both their names; invoices issued before this change print today's details. A company's PO number added after the deposit still reaches an invoice that has none; once money has been taken and the invoice carries a PO, it keeps that one (a refund does not reopen it), and the app says so when the order's PO is changed later. Nobody can type a different PO straight onto a paid invoice.
• Full tax invoice for companies: a customer can carry a VAT number and an address, and an order a company's PO number. A customer with both a VAT number and an address gets a "Tax Invoice" (rather than a simplified one) showing their name, VAT number, address and PO number, in print and in the PDF. The customer form therefore marks the address as needed once a VAT number is typed and does not save without it; a customer saved earlier with a VAT number but no address gets a simplified tax invoice.
• Deposit and balance: one invoice per order, payments and refunds with numbered receipts, and a payment larger than the balance or a refund larger than the amount paid cannot be recorded. A refund needs the owner's PIN, checked by the database, and an order that has taken money cannot be deleted (refund or void, then cancel it). Each receipt can be printed or sent to the customer on WhatsApp.
• Delivery against payment: a piece with a balance is not handed over unless the amount paid covers the pieces being delivered (a fair partial delivery: a father collects two thobes out of five and pays for those two), or through an owner override with his PIN and a recorded reason.
• BenefitPay: the shop's QR code and IBAN are printed on the ticket, invoice and receipt when there is a balance, with a "Show QR" button when paying in the shop.
• Invoice and receipt as a PDF: one tap makes an A5 PDF of the invoice or of a receipt, with the shop's logo, VAT number and BenefitPay QR, and sends it on WhatsApp. On a phone the share sheet opens; on a computer the file downloads and the customer's chat opens so it can be attached.
• Payments: a daily view with receipts, payment methods and the net drawer, and a printable day summary.
• Day close: a cash count by denomination, opening float, cash movements (bank deposit, owner withdrawal, float top-up), expected against counted and the difference, then locking the day: any payment or expense recorded on that day afterwards needs the owner's PIN, and no cash movement can be added to it. Today has a line for a day left open, with Close for the owner and the manager.
• Tailor wages: pay type (monthly / per piece / both), a rate per garment type, a count of the pieces each tailor completed in the month, advances, paid and due, a printed pay slip with a signature line, and the payout recorded as an expense linked to the tailor.
• VAT return: for any period (month / quarter / custom): sales and output VAT, purchases and input VAT, and the net due, with the sales and purchases registers ready for the accountant (CSV).
• Reports for any period: sales excluding VAT, VAT, receipts by method, expenses by category, cost of fabric used, approximate profit, orders delivered and the on-time rate, average ticket, and the most-used fabrics, for a calendar month, today, yesterday, the last 7 or 30 days, this or last quarter, this or last year, or any dates the shop picks. Tailor performance, profit and the accounting export take the same periods (pay slips and the branch comparison stay monthly, because pay is monthly), and the CSV and Excel files are named after the period.
• Dues: who owes what across all open invoices, split into still in the workshop, ready but not collected, and already handed over with a balance; the age of each balance (up to 30, 31–60, 61–90, over 90 days); one WhatsApp reminder per customer covering all their orders; ready orders waiting more than a set number of days with a collection reminder; and a CSV export.
• Activity log: who changed a price, discount or date and when (with the owner's reason), and who voided a receipt or an invoice; changing a price or discount after invoicing is locked behind the owner's PIN in the database itself, not only on screen. It also records every refund, expense, cash movement, day close, stock purchase or adjustment, import, data wipe, deletion (with a copy of what was deleted), order below the minimum deposit and PIN lockout, each with the person who was signed in. Nobody can edit or delete it, the owner included, and wiping the shop's data keeps it.

9The numbers: profit, performance, accounting

Profit

• Profit per order = net sales − fabric cost − accessory cost − piece-rate wage, with the margin; shown to the owner on the order screen.
• Tables by fabric and by garment type for each month, on the same basis as the order profit (after discount, without VAT), with CSV export. This is profit before fixed expenses; the month's net is in the reports.

Tailor performance

• For each tailor in the month: pieces completed, average days to complete, on-time rate, rework, what they hold now, and stalled pieces (in their stage for more than twice the set time).
• Average duration per stage — cutting, stitching, fitting, finishing — with the slowest stage highlighted.

The owner's daily summary

• In Reports (Today's summary), for the owner and the manager only, opened from the money card on Today, in three columns: Today (new orders and their value, money in compared with yesterday and by payment method, expenses, pieces finished and delivered, and what failed the quality check) and Tomorrow (pieces due tomorrow that are not ready, fittings, deliveries).
• And "Needs your attention": late pieces and pieces at risk, pieces that failed QC and are waiting to be fixed, fittings with no appointment, today's deliveries not out yet, pieces ready for over a week, and balances outstanding on ready orders. Each line opens its list in one tap, and when nothing is stuck the card says so.

Accounting export

• Balanced double-entry journal for the month: invoices to customer receivables, payments by method, output and input VAT, expenses by category, and accessory sales in a separate account.
• An Excel file (journal, trial balance, sales, receipts, expenses) or a CSV that imports into Zoho Books, QuickBooks and Odoo. The chart of accounts is editable to match the shop accountant's own.

10Store, stock and purchasing

Accessory sales (the counter)

• The "Store" tab: a fast selling screen with product tiles, a cart and quantities, a named customer or a walk-in, and a payment method; a sale creates a tax invoice and a receipt and reduces stock at once.
• Categories: ghutras and shemaghs, agals, sirwals, undershirts, cufflinks, perfumes, ties, belts, pocket squares, sheilas, veils and scarves, buttons and trims — with sample products matched to the shop's specialty.
• Product stock: selling price, cost and reorder level, stock-in, stocktake, a "low" alert, and stock value at cost. Adding stock, the stocktake, the cost column, stock value, the opening quantity and changing a product's price are for the owner and managers only, as on the fabrics screen; other roles can add a product with its selling price and edit its name, category, SKU, reorder level and active switch.

Fabrics and expenses

• Rolls by code, name, colour, supplier, cost per metre and selling price; the metres on hand update from movements: purchase, use (deducted when the order is recorded), return (on cancellation), adjustment, waste.
• A low-stock line on Today (Add purchase for the owner and the manager) and an alert while recording an order, and stock value at cost.
• Expenses with editable categories, a receipt photo and input VAT, and advances and salaries linked to the staff member.

The digital fabric book

• Customer view on a tablet, full screen: fabric photos, colour, composition, price per metre, and "available / limited / sold out", with search and a colour filter. It shows only the fabrics that are in the book, without the show / hide switches. Opening it drops the owner's unlocked PIN, and leaving it, whether by the X, the back gesture, a link or a reload, locks the device to the name screen, so whoever takes the tablet back types their PIN.
• A link for customers sent by WhatsApp: they see fabrics and prices only — no cost and no quantities — and an "Ask the shop" button. Any fabric can be hidden from the book, and the link can be switched off; a link belongs to one shop only, and once switched off it never opens another shop's book.

Suppliers and purchasing

• A supplier register with payment terms, and purchase orders for fabrics and products, sent to the supplier by WhatsApp and printed on A4.
• Receiving puts the quantities into stock at purchase cost and updates the item's cost. Each supplier's balance = received − paid, and a payment is recorded as an expense automatically.

11Delivery to the customer

• From the order screen → More → "Deliver to customer": the address, date and time, the driver, and a delivery fee added as a line on the invoice.
• Deliveries list: "Out for delivery" sends the customer a WhatsApp message with the driver's name and the balance due; "Delivered" records the recipient's name and a proof photo, collects the balance and closes the order; "Failed" takes a reason and allows a retry.
• The driver sees "My deliveries" on the "My work" screen with a map link and a call button.

12Printing and documents

Every document is bilingual (Arabic first) with a preview before printing, prints in light colours even when the device is in dark mode, and carries the shop's logo and colour on every sheet. Amounts carry the shop's own currency (BHD, SAR, KWD…) on tickets, invoices, receipts, the day summary and the invoice, receipt and quotation PDFs, and receipts and an invoice's payment lines show the full date with the year.

13Ease of use and the interface

• Navigation: on a computer or a wide tablet (1024 px and up) a side bar groups the sections: Today, Orders, Customers and Workshop (My work, the board, the cutting list, the calendar), then under "Shop management" Finance (invoices, payments, expenses, reports) and Inventory & store (fabrics, the store, purchasing), with Settings (and the Platform for its operators) apart at the foot. Each person sees only what their role opens, a group with nothing in it is left out, and the current section stays marked whatever link opened it. On a phone or a narrower tablet an app-style bottom bar (Today, Orders, ＋ New order, Customers or "My work", More) takes its place, and windows slide up from the bottom. More shows only what the bar does not, in the same groups as the side bar, then the person, the language and the theme.
• One interface for everyone: every tab and every order step is always visible, with no "simple" and "advanced" modes hiding anything from the staff. Speed comes from shortcuts — quick add, amount buttons, the next step on every order — not from hiding features.
• Today: the title and the shop's date with New order and Quick job, one search for customers and orders, and three summaries (late, due today, ready to collect), each counting orders with their pieces under it and opening Orders on that filter. Under them "Needs you" puts the most urgent first: late work (the oldest promise first, and fittings whose day has passed), then today's work (orders due today, today's fittings by their time, fittings with no time, orders at risk of being late), then ready orders (not told yet, then told and still waiting after the shop's reminder days), then the shop's notices (yesterday not closed, the setup, fabric running low) and what is coming (re-measuring, the season). Each line names the customer and the order, says why it is there, where the order stands and who has its pieces, and has one button; one line per order, the first lines on the screen, and "All" opens every one, grouped. The owner and the manager also get a small money card (taken today, still owed, with the currency) that opens the day's summary in Reports. The front desk gets the same screen built around the counter: Counter sale beside New order, a search that asks who is at the counter, and the orders ready to collect with one action each (tell the customer, take what is owed, or hand over after a question), then the rest of "Needs you". A part that cannot be read (no connection) says so instead of showing zero.
• Orders: one row per open order with the same things in the same places: the customer and the order number, the garments and how many pieces, the date in words (how late, due today, at risk, how soon, or how long a ready order has waited and what is still owed), the stage (that of the piece furthest behind, "stitching to finishing" when the pieces are spread, how many are finished) and who has the pieces (one or two names, or "Unassigned"). Red is for late, amber for today and at risk, green for ready, and ordinary progress stays quiet. A row opens its order; its one action, where there is one, is a button of its own beside it. Wide lists line the rows up under column names; on a phone each row is a card. The search, the filters with their counts and the Views (board, every order with filters, calendar, cutting list, collections, deliveries, quotations, paper tickets) are as before.
• Easy to read and to tap: text is 16 px and nothing on screen is smaller than 13 px; every button, field and switch is at least 44 px tall, and a screen's one main button is larger still, on a phone, a tablet and a computer alike.
• No sideways scrolling on the phone: lists, alerts and an order's stage tracker fit inside the screen width however long they get.
• Lists on a phone: invoices, payments and expenses show one line each with one amount (what is still owed, or the total once paid) instead of a table that scrolls sideways; invoices filter with All / Unpaid only chips; a receipt's print, PDF and Void sit in a sheet. Reports pair their numbers two to a row, list payroll, VAT and the branch report with the other reports, and fold the lists under the numbers; profit shows the ten biggest orders first. Quick job keeps its alteration sizes, extras and notes behind «Job details». The customer page has one main button (New order), with Edit and Merge under More and the customer's orders as one line each; the cutting list's tick boxes are 44 px and the whole row ticks them; the store counter's categories slide in one row and the cart's count and total stay in view while picking. Fabrics, suppliers and payroll are one card per row too (a person's pay breakdown and its buttons open in a sheet), and stat boxes pair up two to a row on every phone screen.
• Settings as a list of short sections: one row each, with what is inside, under five headings (General, Money and policies, Workshop and templates, Team and branches, Data and system); a section opens alone with a way back, and «Every setting on one page» still shows them all. WhatsApp messages show as the customer would read them, filled with made-up details, each with Edit for the Arabic and the English; the season message sits with them, and expense categories have a section of their own.
• The order screen: the order's number and state, the customer with Call and WhatsApp (every message in one place: the ticket, ready, the balance, a late apology), a stage tracker for the whole order, and one next step chosen from the order's state: tell the customer it is ready, take what is still owed, hand it over, set or finish a fitting, for a late order review its pieces and date (the delivery plan) with the apology as the second button, hand over the pieces already done, or give pieces a tailor. The promised date is always written out under the number, and pieces at different stages are said in words under the tracker. Alike pieces share one card with their pictures; a piece's More holds its price, tailor, photos, cancel, rework, price change, branch and fitting, and lets the owner set its stage (stages otherwise move on the board and in My work). The money is one balance with Record payment. Printing the ticket and the invoice, the PDF invoice on WhatsApp, the PO, the discount, reorder, add a piece, change the date, delivery and bag tags sit behind More; the history folds away; Cancel and Delete sit apart at the bottom.
• A new shop's first day: a "Start here" card with three steps — add your first customer, record your first order, print the ticket or send it by WhatsApp.
• Look and feel: a calm, warm workspace: light paper, clear panels and fine lines rather than shadows, 12–14 px corners, and pills kept for statuses and filters, with a single brand colour, terracotta, and green, amber and red kept for states, always beside words. The Thmanyah typeface for text and headings, a dark mode, and right-to-left Arabic with complete English.

14Branding and settings

• The shop's logo, primary colour and Instagram account, and the interface installs on the phone's home screen like an app. The shop's colour replaces the terracotta in its interface and on its paperwork.
• Staff: name, role (owner, manager, front desk, tailor, cutter, driver, general staff), PIN, wage and language; deactivate and reactivate; change PIN; remove a person from the team (owner only): they can no longer sign in and their unfinished pieces go back to unassigned, while their orders, payments, pay and activity history stay; removed people are listed apart and can be brought back with the same PIN.
• Garment library: the nine specialties and 67 garments, each with a full field editor (add / rename / deactivate a field, priced options, the tailor's rate, and the "needs fitting" switch). A list field's choices are edited in plain boxes (Arabic and English name, extra price, the default, add, reorder, remove), and an On card box picks the measurements printed on the measurement card. A removed choice disappears from new orders but keeps its name and price on the orders that used it.
• Measurement unit: inches (default) or centimetres, reflected at once on every screen and printout.
• WhatsApp message templates (tap a detail such as "Customer name" to put it in the message; a section you edited is marked until saved, and leaving Settings with unsaved changes asks first), deposit and rush policy, capacity and days per stage (including fitting), rail locations and collection hours, free-alteration days, re-measure periods, default delivery fee, numbering, paper size.
• Backup: a full export to a single file (with the owner's PIN) and its import, plus demo data that shows the system off. Importing a backup or wiping the shop's data also asks for the shop account's password again. The file carries the shop's people (never their PINs) and its settings: a restore puts the order prefix, VAT and fees back, and every assignment and receipt follows its person, matched by staff number or name; someone the shop no longer has comes back inactive, waiting for a PIN.
• The demo data: a tailoring house that sews across every specialty — men's thobes, an abaya ready for delivery, a bridal gown with a fitting tomorrow, a suit on its second fitting, monogrammed shirts, school uniforms for a family with a piece per child, a restaurant uniform with its staff list, and South Asian wear.

15Security, data and working offline

• One shop login (email and password) on every device, then each person picks their name and enters their PIN, so every payment and every piece move is attributed to them. Five wrong PINs lock the account temporarily, for 5 minutes, then 10, 20, 40 and never more than 60, counted once per person across branches, so a colleague on the shared login can neither keep the owner out for hours nor guess a PIN in practice (the screen counts the tries left, then says how many minutes the lock lasts). The PIN pad also takes Arabic-Indic and Persian digits typed on a keyboard. The device locks itself after a period of inactivity, counting only touches, clicks and key presses: screens refreshing with other devices' changes do not keep someone signed in, and a device that wakes up after the limit locks at once. Switch user locks the device too: the person signs out and the next one picks their name and types their PIN. Both close any open window without saving what was typed, and the next person starts on their own home screen. Closing the browser locks the device as well: a page the browser brings back later ("continue where you left off") asks for the PIN, and only a reload keeps the person signed in.
• Access by role: the owner sees everything; the manager every screen and report except Settings; the front desk customers, orders, store, invoices and payments; the tailor, cutter and driver only "My work" and the orders board — and no prices on their screens: no amounts, no invoice, no payments. Prices are hidden there, not locked (an order's prices stay readable to the shop's own login); what the database locks is the money behind the counter, below. Each person enters their PIN and the system opens on their own screen. The money behind the counter (expenses, the day close and cash movements, wages, suppliers and purchasing, the activity log and the nightly backups) is the owner's and the manager's, and the database enforces it: each PIN opens a 12-hour session for that person, so a staff device cannot read or change any of it, even from outside the app. Stock purchases and adjustments, cost and selling prices and seasons can be changed only by the owner or a manager, which the database enforces too; other roles can still read them (the order form needs fabric prices and seasons), and costs are hidden on their screens, not locked. Every record carries the person who was signed in, whatever the device claims, and tailors and drivers cannot assign pieces (piece-rate pay follows the assignment). A link to a screen that does not exist, or that the person's role does not have, opens their own home screen instead: tailors, cutters and drivers never get the Dashboard or the fabric book, the fabric book follows the Store tab and the setup checklist follows Settings.
• The owner's PIN is required for sensitive actions: voiding a receipt or an invoice, deleting, changing settings, editing a price or discount after invoicing, delivering with a balance, overriding policy, merging, wiping. The server verifies it every time.
• Protected connection and owner session: the site runs over HTTPS only, with strict browser security headers (it cannot be embedded in another site, runs no script but its own files, not even a line written into a page, and is allowed no camera, microphone or location: a quality-check photo is taken with the phone's own camera through the file picker); anything typed into the system is shown as text and never runs as code, and exports cannot carry spreadsheet formulas. The installed app checks every file it keeps on the device before using it, and a security update reaches every device at its next safe moment (the name screen, or when the app is out of sight) instead of waiting for someone to tap "new version". Photos (the logo, the payment QR, an order's photos) can be added but never replaced or deleted, so nobody can swap the shop's BenefitPay QR. A link that signs in (a password reset, an email confirmation) first shows which account it opens and waits for a yes. The owner's PIN opens an owner session of up to 12 hours on that device, which ends when the user switches, the device locks for inactivity or the shop signs out; typed on someone else's session (to unlock a closed day for the cashier, say), it opens a 5-minute owner session for that one action only; repeated wrong PINs lock for longer each time, up to 60 minutes.
• The shop's data belongs to the shop: Taf9eel is a hosted service, and every shop's records sit in one shared database (Supabase, in Mumbai) where row-level isolation walls each shop off so that no shop can read another's; a full export at any time, and automatic nightly backups that can be restored. Signing out, signing in to another shop or switching branch clears the previous shop's lists from the screen, so no other shop's customers turn up in a picker.
• Privacy, terms and data deletion: public pages in Arabic and English on taf9eel.com say what is stored and where, the terms of the subscription, and how a shop or a shop's customer asks for data to be deleted. Sign-up links to them, and the site has a sitemap and a robots file for search engines.
• Working offline: when the connection drops, operations are saved on the device — moving pieces between stages, a new order, a payment, a customer, a measurement, an expense — and sent in order as soon as the connection returns. Screens keep working from the last saved data with the pending changes shown, and a bar shows how many operations are waiting to be sent. Ticket and receipt numbers are assigned at sync. Excel export and spreadsheet import work offline too on a device where the app is installed. If the app opens again while the connection is down (pull to refresh, a reload, the tablet restarting it), it starts from a copy of the shop kept on the device: the shop's login and the saved data stay, the name screen opens, and after a pull to refresh the person who was signed in carries on. On a device that has no copy yet, the app says there is no connection, keeps the login, and opens by itself when the connection returns. Signing in with a PIN needs the connection, so while it is down a device that locks (inactivity, Switch user, leaving the customer view) opens again only for the person who was using it: their PIN is checked on the device itself, within 12 hours of their last sign-in, and after five wrong PINs the device waits for the connection. Anyone else is told that signing in needs the internet. Each saved change belongs to the person who made it: it is sent only while that same person is signed in on the device, never under someone else's name and never while nobody is signed in; other people's changes wait for them (the list says whose), and a change that cannot be shown to be theirs waits for their review. The owner's and the manager's money screens are kept in the page's memory only, never stored on the device. Signing out ends the session on this device only and needs the owner's PIN; with changes made offline still waiting, or refused, it asks first: Sync now, Sign out anyway, or Cancel (on the name screen, the new-shop screen and in Settings).
• Protection against duplicates: a phone number already on file is refused even offline; if another device added it in the meantime, the saved orders are linked to the existing customer at sync. A rejected operation appears in a list for review and does not hold up the rest.
• A local demo mode: the full system on one device with no account at all, for trying out and presenting.

16Branches

• A branch is an independent shop with its own customers, orders, fabrics, numbering and staff, including its own invoice, receipt and quotation prefix (the main shop's prefix plus the branch letter, such as INV-M), so a branch under the same VAT number never repeats the main shop's tax invoice numbers; it is created from Settings with the owner's PIN, garments and staff are copied into it (each colleague keeps the same PIN and staff number, and stays one person: removed, given a new PIN or locked out after wrong PINs, they are so in every branch), and you switch between branches from the top of the page.
• One subscription for the shop and its branches: the main shop pays for every branch (BD 50 a month each), and a branch follows the main shop's plan, trial and paid-until date, so one payment renews them all and a lapsed main shop turns its branches read-only too. A new branch has no free trial: the subscription says how many shops it covers (the main shop included), set by Taf9eel when the shop asks for another branch, and New branch opens only while there is room (Settings → Team and branches shows how many are covered and how many are open; when it is full, a button asks Taf9eel on WhatsApp). A suspended branch frees its place. A branch's Subscription screen names the main shop to pay from.
• Branch report: one month and all branches side by side — sales, pieces, on-time delivery, expenses, approximate profit, outstanding balances and wages due, with the total.
• Shared customers: a Muharraq customer walks into the Riffa branch; he is searched for across the other branches and his latest measurements are copied to the current branch in one tap, instead of measuring again.
• Fabric transfer between branches as two matching movements (transfer out / transfer in) with metres, cost and a note; if the roll does not exist at the other branch it is created with the same code.
• Piece transfer to be sewn in a quieter branch's workshop: it appears on that branch's board marked with the origin branch and its tailors move it along, while the invoice and the delivery stay with the branch that took the order. The workshop branch can move the piece, assign a tailor and add notes and photos; the price and fabric stay with the origin branch.
• Staff across branches: a staff number (any number the shop chooses, not the person's ID card) links a tailor who works at two branches, so he appears on one line in the branch report and gets one pay slip that adds up his pieces from every branch.

17Taf9eel as a product: setup, countries, subscription

• Shop setup in 6 steps: the shop, country and VAT, specialty, garments and prices, staff, fabrics, and a test print and message; you can stop and continue later, with a progress line on Today. The owner types the PIN twice, and VAT is switched on only when the shop says it is VAT-registered and gives its VAT number and address.
• Country: Bahrain, Saudi Arabia, Kuwait, the UAE, Qatar, Oman — currency, decimal places, dialling code, VAT rate and time zone are set automatically.
• Subscription: a 7-day trial with every feature, then a monthly or yearly plan chosen from Settings. Payment is by bank transfer or BenefitPay: the shop owner taps Pay by transfer or BenefitPay on WhatsApp, which opens a WhatsApp chat with Taf9eel with the plan and the shop ID filled in, and once the money arrives the operator records it from the platform panel, which reopens the shop at once. A warning before expiry, a grace period, then a "read-only" mode, enforced by the database itself and not only by the app, that keeps the data, backups and the customers' tracking page available, and a payment history per shop.
• The yearly plan in instalments: the yearly price can be paid in 4 parts (BD 125 every 3 months). Each instalment moves the paid period on by 3 months and the shop stays on the yearly plan, so the renewal warning, the grace period and the read-only mode work as for any payment; the operator records it as "Yearly plan instalment" and the payment history says which payments were instalments.
• A demo for every kind of tailor: thobes, suits, shirts, dresses, abayas, bridal and evening, school uniforms, company uniforms, South Asian wear, alterations, and a house that sews everything. Each demo has its own shop, garments, fabrics, customers and orders in every stage, with separate data that never mixes; it opens from a direct link on the landing page or from inside the system (on a phone, from the demo chip under More), and can be reset. A demo's running costs follow its own orders, so its reports and cash drawer show no loss on any day, and its WhatsApp buttons open WhatsApp with the message but no number (the demo's numbers are made up), so the person picks the chat; its call buttons dial nobody and say so.
• The platform panel for the operator: every shop with its plan and activity, record a payment, extend a trial, and a Manage button that opens the shop in the super-admin console (plan, dates, suspend / reactivate). Each shop shows its owner's name, sign-in email and phone with a WhatsApp button, a New badge for the first 7 days after it signs up, the paid-until date once it pays, and the short shop ID that appears in its payment message. A Support button on each shop shows who is locked out after wrong PIN tries and unlocks them, or sets a new PIN for anyone in the shop, the owner included when they forget theirs. Each change goes into the shop's activity log as Taf9eel support, and the operator still never sees the shop's own data. Like the console, it answers only a two-step sign-in, so in practice the operator works from the console below.
• The super-admin console at /admin: the operator signs in with their own email (no shop, no PIN) and a code from an authenticator app (two-step sign-in, set up on the first visit, which lasts only while its browser tab is open and ends after 15 minutes without input, when the next sign-in asks for the code again), and controls every shop and sign-in from one place. A dashboard (shops, paying, on trial, read-only, revenue this month, sign-ins, new shops per week, revenue per month, and a list of shops that need a look); every shop with search, filters, sorting, pages and a CSV export; a page per shop to edit its details, set the plan (trial, monthly or yearly), status and dates, record a payment, extend the trial, set how many branches the subscription covers (a payment's amount is the price times that number; a branch shows its main shop and has no payment of its own), suspend it, or delete it for good (only once suspended, only after typing its short ID, and a main shop only once its branches are gone); its sign-ins (send a reset link, set a password, confirm the email, sign out of every device, block); its people with PIN support; its payments and its support history. A sign-ins screen for every account on the platform, a payments screen across all shops, the console's own activity log, and the list of admins. Every action is logged, and each one that touches a shop also goes into that shop's activity log as Taf9eel support. Counts only: the console never shows a shop's orders, customers or money, and cannot export them. Deleting a shop keeps a copy of its activity log in the console's log; its nightly backups are removed 30 days later.
• A public landing page in Arabic and English: a "for every tailor" section with the nine specialties, a gallery of real screenshots (home, workshop board, picking by picture, the phone screen), features, pricing and FAQs, and an instant demo button with no sign-up.
• Installs as an app (PWA), checks the database version automatically, and this document comes in Arabic and English editions.

18Requirements and running it

• Any modern browser on a phone, tablet or computer; nothing to install.
• An ordinary A4/A5 printer, or an 80 mm thermal printer connected to the device.
• Nothing to host or set up: Taf9eel is a hosted service at taf9eel.com. The shop signs up once and every device signs in to the same shop; the data lives in one shared database (Supabase, Mumbai region) with row-level isolation between shops, and the site is served by Vercel.
• WhatsApp: tickets, invoices and reminders open in the shop's own WhatsApp through direct links, with no extra subscription. Automatic messages are optional: they need the shop's own WhatsApp Business number connected to Meta's Cloud API, and Meta charges those messages to the shop's account. The Taf9eel subscription is paid by transfer or BenefitPay; there is no online card payment for now.

19Appendix: the complete feature list

Taf9eel · تفصيل · Version 2.4 · October 2026