Neighborhood commerce · merchant operating system

Connect the customer screen to the real shelf, real stock and real staff workflow.

My Accra International Market combines customer discovery and pickup intent with inventory, receiving, QR/barcode location mapping, owner/admin operations, fresh-item availability and community merchandising. The current program emphasizes truthful state and brand no-drift rather than decorative storefront claims.

Real merchant use caseCustomer + admin routesImmutable brand controlsProduction backend/payment gates remain
Customer experience

Browse → understand → reserve → pick up.

Storefront

Culturally relevant discovery.

Categories, featured products, weekly specials, store information, directions, mobile contact and product search support a practical neighborhood grocery journey.

Account + loyalty

Customer identity beyond a cart session.

Account, loyalty, notifications and order-status concepts support repeat relationships rather than one-off browsing.

Recipes + community

Content connects to commerce.

Recipes, ingredient bundles, store updates and community content create a legitimate path from cultural knowledge to product discovery and pickup.

Store operations

Receiving → inventory → aisle/shelf → scan/pick → order.

Inventory

Know what exists and what is sellable.

SKU/barcode identity, quantity, on-hand/reserved/available state and out-of-stock handling underpin the customer experience.

Receiving

Move supplier deliveries into controlled stock.

Receiving has its own workflow so quantities and product identity survive the handoff from delivery to inventory.

Aisles / shelves

Map digital products to physical locations.

The shelf-label/QR model supports aisle and bay mapping so staff can locate products consistently during receiving and picking.

RBAC

Owner and staff actions stay distinct.

Owner, manager, receiver, picker and other roles should have bounded authority rather than a single universal admin account.

Fresh/perishable module

Availability windows matter for fresh food.

Hot Fresh

Time-sensitive prepared food.

Banku/tilapia, waakye and similar items require explicit availability windows and pickup timing rather than generic always-in-stock logic.

Weekend Fresh

Limited availability without customer confusion.

Watchlist items such as Tsofi, banku and kenkey can support back-in-stock alerts and bounded pickup windows.

Bundles

Merchandising can follow availability.

Fresh bundles and recipe-linked ingredient sets are layered on top of actual inventory truth, not invented stock.

Current status

Strong merchant architecture, controlled production claims.

Brand systemNo-drift controls

Canonical brand variants and immutable asset fingerprints are represented in the production renderer and gate logic.

Customer + adminImplemented surfaces

Storefront, account, loyalty, inventory, receiving, aisles, scan/pick, orders and promotion concepts exist.

GatedBackend/RBAC/payments

Production backend linkage, staff authorization, payment provider/webhooks and deploy verification remain required.

Field proofNext evidence

Catalog completeness, QR shelf mapping and real staff/customer acceptance must validate the operating model.