Documentation

What is wallmarkets?

wallmarkets helps suppliers keep deliveries, returns, products, and supermarket accounts in one working system. Use it to create clean delivery records, link returns back to original shipments, and review the numbers in reports and analytics.

Quick Start

Mobile Access

On mobile devices, you can install wallmarkets as a Progressive Web App (PWA) for faster repeat access and limited cached browsing when connectivity is shaky. Learn how →

Creating a Delivery

Navigate to Deliveries > New Delivery. Select the target supermarket and branch, add one or more products with quantities, choose a delivery date, and submit.

The resulting detail page becomes the source record you can review, print, export, or use as the starting point for a linked return later.

Delivery Record Shape

supermarket: E-mart
branch: Central Branch
delivery_date: 2026-03-15

lines:
  Whole Milk 1L x 50 @ 2850
  Greek Yogurt 500g x 30 @ 4200

The important part is not the format itself, but that destination, quantities, and prices are correct before the record is saved.

How Deliveries Show Up In The App

The current workflow is centered on a clean record rather than a deep status machine. In practice, teams move between the list view, the detail page, and any linked return records.

List Reference

Tracking & Filtering

The deliveries page is a dated working list. Use it to open records, export CSV, review values, and spot which deliveries already have linked returns. When something needs explanation, move into the delivery detail page rather than trying to infer too much from the table alone.

Processing a Return

Go to Returns > New Return, or start from a delivery detail page. Select the original delivery, confirm the product(s) and quantities being returned, choose the return date, and save the record.

Every return stays linked to the original delivery, which is what keeps the history readable later in reporting and follow-up work.

Return Validation Rules

Linked Records And Documents

Each return keeps a direct relationship to the original delivery and can be reviewed, printed, or downloaded as a PDF. That linked structure is what makes later analysis and reconciliation easier than trying to track returns as free-floating notes.

Return Analytics

The reporting views make it easier to read return totals beside delivery totals, then filter deeper by supermarket and category in analytics when a pattern needs explanation.

Managing Your Product Catalog

Each product has a name, weight, price, and category. Products are assigned a unique sequential ID used across deliveries, returns, and reports. Add products individually or import a batch via CSV.

Edit existing products from the product detail page. Changes to price or weight apply to future deliveries only — historical records are preserved.

Product Data Model

CSV Import

Bulk-add products by uploading a CSV file. The importer validates each row and reports any errors before committing.

name,weight,price,category
"Whole Milk 1L",1.03,2850,"Dairy"
"Greek Yogurt 500g",0.52,4200,"Dairy"
"Orange Juice 2L",2.10,5600,"Beverages"

Product Categories

Organize products into categories (e.g. Dairy, Beverages, Frozen) for easier filtering in the delivery form and for category-level reporting. Categories are user-defined — create whatever groupings make sense for your business.

Supermarket Accounts

Each supermarket account represents a chain you deliver to. Within that account, you can register branches with their own address and contact details. This structure keeps deliveries and returns tied to the right receiving location instead of flattening everything into one chain-level record.

Branch Hierarchy

Adding a Supermarket

Branch Record Fields

Branch records are most useful when they contain the details your team will actually rely on during delivery creation and later review.

name: Central Branch
address: Peace Avenue 10
contact_person: Receiving Manager
phone: +976-...
email: central@example.com

The sharper the branch data, the easier it is to avoid destination mistakes later.

Branch Management

Use the supermarket and branch pages to keep names, addresses, and contacts accurate. Clean branch data pays off later in delivery creation, returns, and reporting.

What B2B onboarding creates

B2B onboarding turns shelf access into a tracked workflow. A supermarket owner can open a buyer portal, publish what each location is willing to receive, review local supplier pitches, message the supplier, approve or decline the pitch, and start the first stock request. A supplier can open the same portal from the supplier side, send a shelf pitch with catalog proof, then coordinate requests, deliveries, invoices, and payment follow-up after approval.

Supermarket buyer onboarding

Use this path for an eMart-style owner or category buyer who wants to receive pitches from local brands and decide what belongs on physical shelves.

Local supplier onboarding

Use this path for a food producer, packaged-goods brand, or wholesaler that already has products and wants to show supermarket buyers why the products deserve shelf space.

Lifecycle reference

Operational screens

Where to go next

Dashboard KPIs

The main dashboard gives you the fast read most teams need first: revenue, net revenue, deliveries, and returns over the selected period. The point is not to admire the cards. It is to notice when one of them starts telling a different story from the rest.

Available Report Types

Generating Reports

Navigate to Reports in the sidebar, set the date range, and review deliveries and returns together first. When you need a deeper explanation, open the analytics dashboard and filter by supermarket or category.

API Endpoint Preview

GET /api/dashboard/stats?range=30d

{
  "revenue": 12450000,
  "net": 11200000,
  "deliveries": 156,
  "returns": 8,
  "period_change": "+12.3%"
}

Profile & Password

Update your name, company, email, avatar, and username in Account Settings. The same page also gives you password change, language preferences, notification toggles, privacy links, and the account deletion action.

Go to Account Settings →

Current Access Model

API Keys

Generate named API keys in Account Settings > API Keys. Copy the key when it is shown, store it safely, and revoke it when the integration no longer needs access.

Key name: Production ETL
Rate limit tier: standard
Best practice: one key per integration
Action when retired: revoke immediately

Billing

wallmarkets offers plan-based access, but not every account exposes a full self-serve billing workspace directly in the app. Treat billing changes as owner-level work and use the billing guide when the path needs clarification.