Samisoftz
Book a call

E-commerce

A custom ecommerce back office for orders, returns and stock

A custom ecommerce back office for orders, fulfilment, returns and admin, connected to your store, marketplaces and warehouse.

Orders, returns and stock · ERP where there's an API · Admins on projects we've worked on

The order has too many homes

Shop orders, marketplace orders and live-show orders should not live in three admins.

Fulfilment, returns and stock are already a process. The platform's admin shows one slice of it. Marketplace orders sit somewhere else. A live show adds holds and a pile of orders that belong to that stream. Staff jump between screens, and the warehouse sees a different list from the person writing to the customer.

We build the admin around that process: orders, returns and stock in one place, connected to the store, the marketplaces and the warehouse. We connect to your ERP and warehouse where they offer an API. We confirm that on the call. Live-show orders and holds can sit here too, with a report per stream.

Projects we've worked on include a stock and credit ledger for a trader (who owes what, what's in stock) and admins for a car hire site and a live-shopping app.

What we build

The work your team already does, in one admin, with a person still sending anything a customer reads.

Orders

Shop, marketplace and live-show orders in one queue, in the order your team works them.

Returns

A return has a reason, a state and a place in the same admin as the original order.

Stock

Stock the warehouse can trust, connected to the store and the channels that sell it.

Live-show orders

Holds and orders from a stream, plus a report for that show, not a separate sheet.

Drafts a person sends

Reorder alerts at levels you set. A person sends any reply a customer reads.

In use

A return and the order it came from are on the same screen.

A size comes back. The reason is on the return, the original order is next to it, and the stock count the warehouse sees has already moved. If a reply is drafted, someone on your team sends it.
Connected to your store, marketplaces and warehouse. Your ERP stays.

How it works

We follow an order from the sale to the warehouse, then build the admin around that path.

  1. Call

    Where orders, returns and stock live today.

  2. Brief

    The path, the exceptions, and what must stay in the ERP.

  3. Build

    One admin, connected to the shop, the channels and the warehouse.

  4. Launch

    Your team works a real day in it before we call it done.

  5. Handover

    Code, docs and access are yours. We stay on call for 30 days.

What you get, and what we need

You get an admin that matches the work. We need the process, not a guess at it.

What you get

  • Orders, returns and stock in one place.
  • Connections to the store, marketplaces and warehouse.
  • Live-show orders, holds and a report per stream.
  • Drafts your staff can approve. A person sends them.

What we need from you

  • The path an order takes today, including returns.
  • Access to the ERP we are connecting to.
  • Who is allowed to send a customer reply.
  • Which reports the warehouse already trusts.

Projects we've worked on

  • Trade · Stock

    Stock and credit ledger

    Stock and what is owed sit on one desk.

    What's in stock and who owes what, on one desk.

  • Automotive · Hire

    Luxury car hire site

    The public site and the admin the team uses to run it.

  • Live shopping

    Live shopping app

    Viewers check out without leaving the stream.

    Live video with real-time chat, a cart viewers build together, custom payments, invoices and the admin behind it.

D2C brands

Selling direct, and keeping the customer relationship in your tools.

AI helpers we can add (planned)

  • Reply drafts for customer service

    What we'd propose to measure: First-response time.

    How it's built: Drafts from order data in the help desk or back office. An agent sends the reply.

  • Returns reason grouping

    See why sizes or items come back.

    What we'd propose to measure: Return rate by reason.

    How it's built: Free-text return reasons classified into groups.

Questions

Do you replace our ERP?

No. We connect to it. The back office is the place your team works the orders, returns and stock. The ERP stays the system of record you already have.

What should your back office do better?

Usama, founder of Samisoftz

You'll talk to Usama, who'd build it.

30 minutes · no slides · a written answer if it's not a fit

Book a free 30-minute call