Capabilities · Catalog to handoff
Shop Tek connects a product to its options, price, and stock, then carries that truth into cart, order, packing, handoff, and invoice. The result is not a crowded dashboard. It is an operating record the merchant and team can use to take the next action confidently.
Six parts, one path
Every Shop Tek area hands its data to the next. Staff do not retype color, price, or address as an order moves into fulfilment, and historical order prices do not change when a price list is edited later.
Write product names and descriptions in Arabic and English, then add media, collections, tags, and publication status. The option engine supports color, size, material, or a custom axis, with a documented ceiling of three axes and one hundred variants per product.
Every visit begins at retail, while a customer can be assigned to Wholesale, VIP, or another type. A price list applies at product or variant level, checkout reprices the cart, and the final value snapshots into the order line.
Inventory is reserved during purchase to guard against overselling, and adjustments record their reason. Low items appear in the store dashboard; when an order is refused or cancelled, restocking is a deliberate action rather than an unexplained correction.
An order moves from pending to confirmed, packed, shipped, delivered, cancelled, or refused through defined transitions. Lists surface new work, what must ship, and what needs attention, while the timeline stays useful to operations and support.
Checkout asks for the fields defined by the store country, a normalized phone, and an optional delivery pin. Set local regions, flat rates, free-shipping thresholds, and pickup when it suits the business.
Owner, Manager, Staff, Driver, and Viewer roles receive the appropriate surface. Drivers see their assigned orders while sensitive prices, settings, and refunds stay protected, and stock, price, and refund changes remain auditable.
Complete daily journeys
A capability succeeds when a merchant can finish the job, not when a button exists. These are examples of flows designed to stay inside the system without copying details between tools.
The merchant adds the shirt, its colors and sizes, binds each color to imagery, and sets stock per combination. The buyer chooses red in medium, and the order carries that option, price, and visual reference into packing and invoice.
A customer is assigned to Wholesale, so their list appears at purchase. Checkout verifies price and stock, then the order keeps an independent snapshot even if the owner edits the list the following week.
The team records refusal and its reason, then decides whether the units return to stock. The movement stays visible and the refusal history can inform future COD risk review.
After confirmation and packing, a manager assigns a specific team driver. The driver sees the relevant order, landmark, and collection amount, while the store retains the final status record.
Integration status
Payment, messaging, or e-invoicing may depend on a third party. We separate the capability built into Shop Tek from the external account or approval needed to make it live.
Fees, cap, confirmation, refusal, and restocking operate in-product without an external gateway.
The product creates a dynamic QR and order reference, with operational transfer verification.
Live delivery needs a provider account and approved templates; log and fake drivers support testing.
The e-invoice interface can swap providers, while live submission needs ISTD credentials.
No card provider is approved at launch, so we do not promise an unavailable capability.
Own-driver mode and delivery zones work now; a live carrier network needs an approved provider.
Correctness before spectacle
Money is stored as integer fils rather than floating-point values that can introduce rounding mistakes. The system calculates tax within the displayed price and separates it in documents. Order lines snapshot both price and selected options so invoices and reports remain aligned with what the customer accepted.
Each store operates in an isolated context, and data boundaries are enforced in the application and PostgreSQL database. That does not mean any software is invulnerable, but it means isolation is more than a visual query filter. Support access should remain limited, need-based, and auditable.
Arabic is the native interface state. Field order, icon direction, headings, and mobile behavior are reviewed in RTL first and then mirrored for English. Under a reduced-motion preference, nonessential movement stops so reading and navigation remain comfortable.
Test the path, not the list
The clearest way to understand Shop Tek is to run one complete journey in a trial store and compare it with how your team works today.
14 days, no card · The core plan has no sales commission
