Choose the operating model
Confirm categories, branches, customer channels, staff roles, and delivery coverage.
Bring local store catalogs, customer orders, and delivery workflows into one configurable online commerce experience.
DETA Market is positioned for a business that operates its own local commerce service across grocery, pharmacy, and general retail. Depending on the agreed scope, modules, branches, order channels, and delivery areas can be configured from a central operating model.
Organize daily essentials with categories, product variants, delivery areas, coupons, and a cart-led ordering flow.
Structure medicine and health-item catalogs with brands, categories, inventory controls, and prescription workflows when included in scope.
Present general merchandise such as electronics, clothing, and accessories with attributes, search, filters, and wishlists.
DETA Market is presented here as a local commerce system for an operator managing its own stores and branches. A marketplace with independent sellers is a separate business model and should be scoped separately.
The page describes these as configurable store modules. Confirm which categories and workflows are included in the project.
Mobile customer and delivery experiences can be planned as part of the project. Platforms, branding, and publication responsibilities are confirmed in the proposal.
An offline-first POS flow can be scoped with local transaction storage and later synchronization. Device and recovery behavior must be validated before launch.
Available integrations depend on the country, provider account, and current technical compatibility. The selected integrations should be listed in the project scope.
The technical stack for the DETA Market delivery should be confirmed by DETA Yazılım; no third-party stack is asserted on this page.
Pricing, license, installation, updates, and support are defined in the current DETA Yazılım proposal and agreement.
Confirm categories, branches, customer channels, staff roles, and delivery coverage.
Prepare the catalog, order rules, payment and communication services, then validate the customer and staff journeys.
Test online and in-store workflows, reporting, backups, and training before the agreed release.
Manage catalogs, orders, customers, stock, promotions, delivery areas, and business reporting from a central workspace.
Give each operations point a focused view for incoming orders, preparation, dispatch, and local activity.
Offer a responsive storefront for browsing, cart, coupons, checkout, and order status.
Plan a branded mobile shopping experience, account tools, saved items, and order updates within the project scope.
Coordinate assignments, pickup and drop-off status, route guidance, and delivery activity for the field team.
Central administration, configurable storefront appearance, site-building and content tools, optional AI-assisted content workflows, multiple currencies, multilingual storefronts, and right-to-left layout support.
Organize categories, variants, attributes, multi-category catalogs, search, filters, wishlists, and highlighted or time-limited offers.
Centralize orders, configure delivery or pickup, edit orders through permitted admin flows, and show customers current order-status updates.
Set service zones, fees, opening hours and schedules; coordinate delivery notifications and define refund handling.
Configure redeemable coupons, fixed or item-level discounts, customer wallet flows, loyalty rewards, ratings, reviews, and purchase notifications.
Manage customer and delivery-team records, supported sign-in methods such as email, one-time codes or social sign-in, and role-based access.
Configure supported payment providers, tax rules, invoice formats, and bulk data exports according to the market and project.
Plan push notifications, email templates, customer chat, announcements, blog and FAQ content, sales reports, and flexible delivery charges.
Payment, messaging, mapping, and carrier connections depend on country, provider access, and the approved technical scope.
When offline POS is included, keep the catalog and checkout available on the cashier device and queue transactions for later sync.
Transfer queued orders when the connection returns and apply duplicate protection to avoid repeated records.
Select the serving location and keep its stock, prices, and orders associated with that branch.
Define cash, customer balance, or payment-link options according to the configured payment services.
Plan network or USB thermal-printer support and on-demand receipt printing for the chosen hardware.
Pause an in-progress basket and resume it later without losing the order details.
Support customer lookup and secure staff sign-in; authentication controls depend on the implementation.
Select payment providers based on operating country, account eligibility, and contract terms.
Choose SMS and notification services that are available to the business and supported by the deployment.
Confirm map, routing, and carrier integrations against service areas and provider availability.
Plan server setup, admin access, storefront deployment, and email delivery configuration.
Set branches, catalogs, delivery areas, fees, schedules, order states, and staff permissions.
Scope logo, colors, app identity, sign-in, one-time codes, push notifications, localization, and app-store publishing where applicable.
Define training, documentation, revision rounds, maintenance, updates, and support channels in the proposal.