Stark Consultancy
Built for e-commerce teams past the spreadsheet stage

Shopify, your WMS, and every courier — tracked in one control tower your whole team shares.

I pull your storefront, warehouse management system, and logistics aggregator data into a single platform — so Ops, Warehouse, CX, and Logistics stop chasing five different screens and start working off the same order, the same numbers, the same day. Deployed on AWS or self-hosted, built for teams who've outgrown spreadsheets and need this live before the next funding milestone, not next quarter.

Uptime target
99.9%
Tracking refresh
<2 min
Data pulls / day
Multiple
Deploy target
AWS or local

Services

What the control tower gives you

One cloud-hosted system that gives ops, warehouse, logistics, and CX teams a shared source of truth — deployed on AWS, built to scale.

Order Tracking

End-to-end visibility into every order, from storefront to last-mile delivery, so problems surface before customers ever notice.

Warehouse Control Towers

Real-time SLA and TAT monitoring across warehouses and fulfillment centers, with bottleneck detection built in.

Ops Workflow Tools

Assignment, escalation, and resolution tracking so every issue has a clear owner and nothing sits unresolved.

Interactive demo · the real interface

Run D2C order ops from one screen

The actual layout and information design of the tool: sidebar, tables, and status logic all match what ops teams use day to day. Open the Dashboard, follow one order in Order Detail, then see where time goes in TAT Analytics, Logistics TAT and Courier Performance. Every figure is synthetic sample data.

Five pages are open to explore. Pages marked with a lock are part of the full demo.

app.d2ccontroltower.in
Completed

29

Cancelled

6

Ready to Dispatch

12

Packed

12

Picking

15

Fulfillable

10

Unfulfillable

6

Warehouse Command Center
4 warehouses3 aging 3+ days6 open SLA breachesActive breach rate: 14.3%
WarehouseTotalCOMPLETEDCANCELLEDOPEN / ACTIVEAGINGHealth
CountRate%BreachCountBreachTotalPickPack0d1d2d3d+
WH-Bengaluru17529.4%0119215112Critical
WH-Bhiwandi23834.8%23310358110Normal
WH-Gurugram20735%0108325210Normal
WH-Hyderabad30930%211157411301At Risk
ALL WAREHOUSES902946542151229733

OTF Rate

71%

Follow-ups Today

3

Orders with Errors

19

Escalations (7d)

8

Priority Summary
Critical
5
P0
3
P1
3
P2
4
Normal
4

Order Age (Open)

29
0d
7
1d
3
2d
3
3d+
Order Status Funnel
15
Picking
12
Packed
12
Pickup Pending
25
Completed OTF
4
Completed Breach

Orders, pickup errors, NDR, RTO, team workload and more are in the full demo. Get a personalised walkthrough.

Why teams switch

Everything your ops team needs, in one tool

Built from real order-ops pain points, not a feature checklist — every capability below solves something that used to take a spreadsheet, a Slack thread, and a lot of manual checking.

See everything

One pane of glass

OMS, Shopify, and Shiprocket data unified in a single tool — no tab-switching to piece together what happened to an order.

See everything

TAT analytics

P50 / P90 / P95 turnaround-time percentiles per warehouse, not just averages that hide the long tail.

Move as one team

Role-based access control

Every team sees exactly what's relevant to them — nothing more, nothing less.

Move as one team

Automated mail escalation

Breached orders trigger escalation emails automatically, and replies show up in-tool without leaving the order.

Stay ahead of logistics

Courier partner performance

Delivery success rate, RTO rate, and turnaround time tracked per courier partner — see who's actually performing.

Stay ahead of logistics

Configurable alerting

Set the SLA breach threshold and alert recipients from the tool — tune sensitivity without touching code.

Built to scale, built to fit

API / webhook integrations

Increff, Unicommerce, Shopify, and Shiprocket connect via API or webhook — built to fit the stack you already run.

Built to scale, built to fit

AWS or self-hosted

Deploy fully managed on AWS, or self-hosted on Docker in a server you control — same tool, your call.

Every build above is a starting point, not the whole menu

This page shows one control tower. The actual system gets scoped to your order volume, your OMS/courier stack, your team structure, and your rules — swap in the integrations you need, drop the ones you don't, and deploy it on AWS or your own server.

What actually changes

Where this moves your numbers

Not features for the sake of features — here's exactly what each one fixes for a multi-brand, multi-storefront operation.

One live view across every brand and storefront — nobody exports a thing.

Instead of: Ops manually combines five brand sheets every morning just to know what shipped.

Courier performance tracked per brand and per pincode, so a bad lane gets fixed before it costs you.

Instead of: A courier's NDR/RTO problem shows up in your P&L before anyone notices it in ops.

The right person gets an email, Slack, or WhatsApp ping the instant a breach threshold you define is crossed.

Instead of: SLA breaches get discovered when a customer complains on social media.

Production-to-dispatch visibility flags a stockout risk before it blocks an order.

Instead of: Production and warehouse teams find out about a stockout when the order fails.

Role-based views give every brand manager exactly their slice, live, without a rebuild.

Instead of: Each brand manager wants a different cut of the same data, so someone builds five reports.

Per-order margin tracked as it happens — not discovered a month late.

Instead of: You find out true landed cost (freight + COD fees + returns) at month-end reconciliation.

How the engagement works

Week by week, start to handover

~6-7 weeks, typical
  1. Week 1

    Discovery & scoping

    Map order-to-fulfillment flow across every brand/storefront, audit data sources, agree success metrics.

  2. Weeks 2-3

    Data & pipeline

    Connect OMS, WMS, and courier feeds; build the reconciliation and sync logic underneath.

  3. Weeks 3-5

    Build

    Dashboards, order-detail views, and automated alerts wired to real data, not mockups.

  4. Week 6

    UAT & iteration

    Your ops team runs real scenarios through it; edge cases get fixed before go-live.

  5. Week 7

    Handover

    Training, documentation, and a clean handoff — plus an optional support retainer.

Proven in production

One build, fully deployed

This is the real control tower this page is modeled on — designed and deployed for an actual multi-brand D2C operation. Client name withheld by request; everything below reflects what actually shipped.

Multi-brand D2C group · Shopify + third-party OMS

Warehouse & Order-Ops Control Tower

A cloud-hosted command center that replaced manual CSV firefighting with real-time SLA tracking, automated error routing, and full order visibility across every brand and warehouse.

SLA monitoring

P50 / P90 / P95

Courier refresh

< 2 min

Deploy target

AWS or Docker

A multi-brand D2C group running several Shopify storefronts, fulfilled through a third-party OMS, had outgrown its ops process. Every SLA breach was caught by hand — someone scanning CSV exports, hoping to catch a late order before a customer complained. When something went wrong, there was no record of who owned the fix, no way to escalate it, and no reliable way to tell if the storefront and the OMS even agreed on how many orders existed.

I designed and deployed a fully cloud-hosted control tower on AWS to fix this at the root. A containerized data pipeline pulls order data from the OMS multiple times a day, with API, email, and file-based fallbacks so a single integration hiccup never stalls the whole operation. A rules engine classifies every order error the moment it appears and routes it to the right team automatically. Ops, logistics, warehouse, and CX each get a role-scoped view of exactly what's theirs to fix, with built-in assignment, escalation, and remarks so nothing sits untouched.

Python / FlaskPostgreSQLApache AirflowRedis + CeleryDockerNginxAWS (EC2/ECS)

Share your workflow.

A few details are all we need. We'll reply within 1–3 business days.