You encode size, color and material directly in the SKU —
e.g. SHIRT-COTV.M.WHT.COT, SHIRT-COTV.L.WHT.COT —
and each combination is an independent SKU with its own stock, its own barcode label
and its own price. The common prefix (SHIRT-COTV.*) groups them in reports
and searches, without a separate "parent product" entity.
Three recurring operations in the store — what they look like on SGApps.
The customer brings a t-shirt to the counter. You scan the barcode label —
SGApps sees the exact SKU (SHIRT-COTV.M.WHT.COT),
the price, the seasonal discount (if active), the remaining stock.
All deducted from the specific SKU, not from an aggregated stock.
The winter collection arrives. You prepare in Excel the list of SKUs following the prefix convention (one line per size × color × material combination), with quantity + price, then import the CSV. The system creates the SKUs and generates unique barcode labels per SKU, ready to print on the label printer. Alternatively, add SKUs manually one by one to the catalog.
The customer requests an M → L exchange. You issue a reversal receipt for the M SKU (stock is automatically restored) and a new sale receipt for the L SKU. Both operations comply with MEV requirements for return/reissue. The cashier performs the steps in a guided POS flow — no manual data re-entry.
No separate "parent product" entity — you encode attributes directly in the SKU and reports group them by common prefix.
Each size × color × material combination is an independent SKU:
SHIRT-COTV.M.WHT.COT, SHIRT-COTV.L.WHT.COT,
SHIRT-COTV.M.BLK.MIX. The common prefix SHIRT-COTV.*
groups all combinations of the same model in searches and reports.
Why it matters: separate stock per SKU (not aggregated), price and discount configurable per SKU, and reports that automatically aggregate by prefix — see which sizes / colors sell. You define the naming convention at onboarding.
When you receive a new collection, you prepare in Excel the columns SKU, name, price, quantity (one line per combination following your prefix convention), export CSV and import. The system creates the missing SKUs, updates the stock of existing ones and prepares the labels for printing.
Each SKU generates a unique barcode (EAN-13 or Code-128). Label templates (name + size/color from SKU + price + barcode) for Zebra / Godex / Argox printers. Reprint when labels get damaged or when seasonal prices change.
"SHIRT-COTV.* sold 47 units this month. Detail: M.WHT: 18, M.BLK: 12, L.WHT: 9, L.BLK: 5, S.WHT: 3." You order from the supplier only the sizes / colors that move. You reduce overstock on dead combinations.
The same convention works for accessories too — bags (BAG-XX.COLOR.MATERIAL),
watches (WATCH-XX.STRAP.DIAL), footwear (SHOE-XX.SIZE.COLOR).
It's not limited to textiles.
The flows specific to a clothing store that don't reduce to "one product / one price".
You group products into collections (Autumn 2026, December Gifts). Visual labels on the product, filters in the catalog, reports per collection. At the end of the season, one button — you archive the collection, and the remaining products are marked "old season" for discount.
Discount on collection ("Autumn -30%"), on category ("Shoes -20%"), on specific SKUs ("Only SHIRT-COTV.XL.* -40%") or flash sale on an hour interval. Applied automatically at checkout, crossed-out price shown on receipt.
In the base package the cashier can apply a discount or voucher on a receipt (percentage or fixed amount, with a right configurable per role). We don't store customer data — the receipt is issued fiscally with the discount applied, that's it. Loyalty card with per-person purchase history = separate module, offered as a dedicated upgrade on request.
Fiscal return receipt (reversal) linked to the original receipt. The returned product is automatically restocked on its own SKU. You can refuse the return if the product is dirty / missing a label (a rule configurable per store, not an ad-hoc decision by the cashier).
For a store with 1-2 registers, 1-3 employees, up to ~1500 distinct SKUs — the Micro package covers it.
What's included: POS + multi-attribute SKU catalog + stock + integrated MEV fiscal register + unlimited e-Factura + 1 user + email support. CSV catalog import. Barcode label printing (compatible Zebra / Godex / Argox). 500 MB storage (~500 products with photo). 2 GB monthly traffic.
Extras on request: +80 MDL/month per additional POS (second register / inventory tablet), +20 MDL/month per additional user.
Micro package detailsOver ~500 receipts/day or ~2500 distinct SKUs → Start package (700 MDL/month) — higher ceilings, same features. Upgrade without migration — only the plan changes, the database, configuration and SKUs stay.
See package comparisonThe fiscal register itself (hardware) — you buy it separately from a distributor approved by CIECC. We integrate the software with MEV. Label printer and barcode scanner — we recommend tested models (ADPOS / Sunlux scanners — the most tested with our customers), you buy from our partner or independently.
How the fiscal register worksThe volume figures and uptime targets are indicative for the typical profile of the package. Controlled overruns are accommodated by dimensioned headroom — we don't silently block at the limit. These are not contractual guarantees with financial credit — for a signed SLA, see Enterprise.
Fiscal register, receipt printer, barcode label printer, scanner, cash drawer, POS, management software with multi-attribute SKU catalog, installation, configuration and service — you handle them all through a single contact at SGApps. The difference from a pure reseller: we build the software in-house, we don't resell it — updates driven by real feedback, not by someone else's roadmap.
CIECC-certified fiscal register, receipt printers, Zebra / Godex label printer, ADPOS / Sunlux barcode scanners (the most tested with our customers), cash drawer — we deliver from our partner catalog (SFS-certified suppliers). Base integration is part of the standard onboarding; specific configurations (multi-POS, particular label printer model) are quoted after assessment. Hardware you bring yourself: we integrate it separately, quoted individually after model evaluation.
ERP + POS + multi-attribute SKU catalog + e-Factura + stock on the same instance. Code written by our team, not resold. Updates at the pace of real customer feedback, not someone else's roadmap. Documentation is openly public — you can evaluate before signing a contract.
Full onboarding: POS + fiscal register + label printer configuration, catalog import from Excel / CSV (one line per SKU following your prefix convention), staff training for fashion-specific flows (collections, discounts, returns).
Email with response target and Telegram Mon-Fri 9-18 on Enterprise. You're not left with "your problem now" after installation. Public documentation, playgrounds, examples for the specific clothing management flows.
Fashion retail in continuous production since 2018. The same flows run on our group's own stores — piloted in-house, delivered outside.
Recommended minimum set + options. We're not tied to one supplier — if you already have equipment, we integrate it if it's compatible.
CIECC-certified fiscal register connected to MEV (Datacash, PayLink, Melitax — we integrate with their API). Separate receipt printer optional if you want a receipt distinct from the fiscal one.
Zebra ZD421 / GK420, Godex G500, Argox OS-214 — tested. Adapted label templates (name + size + color + price + EAN-13/Code-128 barcode). Permanent labels and promo labels handled separately.
Handheld scanner Zebra DS2208, Honeywell Voyager or equivalent. USB directly into the POS. Recognizes EAN-13, Code-128, QR (useful for digital vouchers).
Android tablet or minimal touchscreen PC as POS (SGApps runs in the browser — works on anything with a 10"+ display). Classic cash drawer connected to the receipt printer. Card terminal separately from your bank (Moldova Agroindbank, MAIB, Victoriabank etc.).
Want to look at the product first before a discussion? It's public — no mandatory demo call.
docs-services/erp-bom-horeca/ — the complete functional documentation. Includes SKU catalog, collections, and discounts chapters.
tarife/pachete — ceilings, discounts, add-ons per package. No hidden pricing.
/api/ — if you already have an ecommerce or want to sync the SKU catalog with marketplaces (Marketplace.md, StaraGaraj etc.).
We spend 20 minutes together looking at your store — we assess whether SGApps is a fit, what hardware would suit you, how long importing your SKU catalog might take. The initial consultation is free.