Abhishek Rupapara, ecommerce manager, Sydney

Sydney, Australia

Ecommerce manager who builds the systems the team runs on.

I run ecommerce at EveryHuman, a disability and mobility footwear retailer selling direct, through NDIS plan managers, and to hospitals and government health services. I started on the warehouse floor here, so the orders I write systems for are orders I have picked and packed myself.

LinkedIn Download resume abhipatelamr@gmail.com

3

sales channels

Direct, NDIS plan managed, and B2B hospital and government. Three sets of billing rules over one catalogue.

13

systems in production

Roughly 17,000 lines of Python, all written since January 2026 alongside the trading role. The customer care team runs on them every day.

5

platforms integrated

Shopify, Gorgias, Starshipit, Dialpad and Formstack, wired together by hand.

Two doors

Door one

Ecommerce operations

Running the storefront and the trade. Shopify Plus, catalogue and ranging, pricing, bundles, sale launches, stock, clearance, preorders, and the B2B accounts, across three channels that each bill differently.

  • Shopify Plus storefront and theme
  • Catalogue, ranging and product launches
  • Pricing, bundles and promotions
  • Order value strategy, upsells and discounting logic
  • Sale events, including end of financial year
  • Stock, clearance and preorder allocation
  • Affiliate and referral programs
  • B2B and wholesale accounts alongside direct
  • One shoe in four widths, so fitment is the whole decision

For a hiring manager who needs to know I can run the whole function.

Read more →

Door two

AI ops and systems

Building what the role needed. Thirteen systems in production, roughly 17,000 lines of Python, all of it written since January 2026 alongside the trading role. They run against Shopify GraphQL and four other platform APIs and share one idempotency layer so nothing can run twice.

  • Python, running daily against the live store
  • Shopify GraphQL Admin API
  • Gorgias, Starshipit, Dialpad and Formstack integrations
  • A shared idempotency layer reused across seven systems
  • A reporting engine with canonical metric definitions
  • Agentic AI workflows with a draft first, send second rule
  • Per customer parsers for purchase order intake
  • Netlify front ends embedded in intake forms

For a hiring manager who needs to know I engineer rather than configure.

Read more →
The route in

Architecture, then the warehouse floor, then building the systems

  1. 2015 to 2023

    Architecture

    Bachelor of Architecture in India, then a Master of Architecture at the University of Sydney. Architecture taught me how to break messy real world problems into structured systems. It is the reason I draw a system before I build one.

  2. 2023 to 2024

    The warehouse floor, then operations

    I started at EveryHuman as a warehouse associate, picking, packing and dispatching. Seven months later I was running day to day operations across fulfilment and supply chain. Ecommerce gave me the volume and the pressure, and it means the orders I write systems for now are orders I have packed myself.

  3. 2024

    Ecommerce manager

    Took the channel. Shopify Plus, ranging, pricing, promotions, order value, and three billing models over one catalogue. Direct customers, NDIS plan managers who pay the invoice instead of the person wearing the shoes, and hospitals and health services buying on purchase orders.

  4. 2026 onward

    Started building

    From January 2026 I started building the tooling the role needed, alongside running it, because none of it could be bought. Thirteen systems are in production now, about 17,000 lines of Python, and the customer care team runs on them. Not chatbots and not content generators. Real systems handling real tickets and real orders, every day.

How I work

Three decisions, and what I turned down

01

A reader per customer, not one parser for all

Every hospital and government customer sends purchase orders in a different shape. Some put the size in a column, some bury it in a product code that wraps onto the next line. The obvious build is one parser with branches for the exceptions. I rejected it, because each new customer would make that shared parser riskier for every customer already working. Instead each one gets its own reader and they all return the same normalised order. Adding a customer is adding a file, and it cannot break the others.

02

Business rules live in code, not in documentation

One B2B customer ships straight to the patient and must never be invoiced. Written in a document, that rule gets missed at 5pm on a Friday by whoever is covering. So it is not in a document. It is a check inside the script that refuses to raise the invoice. Documentation describes a rule. Only code enforces it.

03

Measure the channel before automating it

Before building anything for support I looked at what the phone line was actually doing over thirty days. It took hundreds of calls and answered a small fraction of them. No amount of automation would have fixed that, because the problem was routing and staffing, not speed. Measuring first changed what got built, and stopped me building the wrong thing well.

The shape of it

One store, six families of systems

System map
System map 01 Order operations 02 Customer care 03 NDIS and B2B billing 04 Merchandising 05 Reporting 06 Shared engineering SHOPIFY STORE ONE CATALOGUE, THREE CHANNELS
System map SHOPIFY STORE ONE CATALOGUE, THREE CHANNELS 01 Order operations 02 Customer care 03 NDIS and B2B billing 04 Merchandising 05 Reporting 06 Shared engineering
Every system reads and writes the same store. The shared layer underneath is what stops them colliding.
The schedule

Six families. Thirteen systems.

Thirteen systems, grouped by what they handle. The 25 rows below are the jobs they do, not thirteen separate products.

01

Order operations

  • Purchase order intake with a reader per customer
  • Preorder allocation, oldest order first
  • Exchange orders with free shipping and tax handled
  • Oversold stock detection across continue selling variants
02

Customer care systems

  • Out of stock handler that finds in stock alternatives
  • Faults workflow that detects the fault type and branches
  • Showroom booking with a form, a calendar invite and a sheet
  • Automated PDF invoicing onto the original ticket
  • Support triage filter, calibrated against real tickets and awaiting release
03

NDIS and B2B billing

  • Seven step NDIS order flow from intake form to invoice
  • Plan manager billing with a maintained plan manager database
  • Payment followup, one ticket per company with invoices attached
  • Payment reconciliation from proof of payment to marked paid
  • Store credit issued against line value
04

Merchandising and inventory

  • Stockout lost sales engine
  • Clearance analysis separating dead stock from slow stock
  • Publishing audit finding active products missing from the store
  • Sizing and fitment data across five brands
  • Price lists for government tenders
05

Reporting

  • Reporting engine with one canonical metric definition file
  • Channel mix, cohort and returns reporting
  • Cost audit that pushed corrections back into the store
06

Shared engineering

  • Idempotency layer reused across seven systems so nothing sends twice
  • Credential handling in one place, never in a script
  • Draft first, send second, as a rule enforced in code
Skills

Grouped by the work that proves them

Ecommerce platform

  • Shopify Plus admin and theme
  • Shopify GraphQL Admin API
  • Catalogue, variants, widths and fitment data
  • Pricing, bundles, promotions, sale events
  • Preorders and backorder policy
  • Google Analytics 4
  • Klaviyo and lifecycle email

Automation and integration

  • Python
  • REST and GraphQL integration by hand
  • Gorgias, Starshipit, Dialpad, Formstack
  • Idempotency and safe reruns
  • Webhooks and scheduled jobs

Analysis and reporting

  • Canonical metric definitions as code
  • Cohort and channel analysis
  • Stockout and lost sales modelling
  • Cost and margin auditing
  • Google Sheets and Drive APIs

Domain

  • NDIS plan managed billing
  • Hospital and government purchasing
  • Disability and mobility footwear fitment
  • Assistive technology delivery and fitting services

Currently certifying: Google Analytics (Skillshop) and Klaviyo Product Certification.

Contact

Ecommerce operations, digital operations and online trading roles in Sydney. Business systems and automation roles as well. Either way the work is the same: run the channel properly, then build the systems that make running it repeatable. Available now and open to talking.

abhipatelamr@gmail.com 0451 267 061 LinkedIn Download resume

Abhishek Rupapara

Sydney, Australia

Ecommerce operations and systems