eCommerce

What is different about eCommerce work

Most underperforming Shopping accounts are data problems wearing a bidding costume. Titles written for a catalogue rather than for search, categories set once and never revisited, attributes left blank, each of those removes products from auctions quietly, and the account looks like a budget problem instead.

What we have built in this sector

A rebuilt product feed and a campaign structure organised by margin and purchase intent for a men’s grooming brand, with data-quality monitoring to catch the silent disapprovals; and a paid-social framework for the same brand that separates awareness spend from conversion spend so the two can be judged separately.

Where an online store loses money quietly

Very little of what goes wrong in ecommerce is visible on the storefront. It is in the feed that describes the products, the returns that are processed late, the listings that drift out of date, and the support queue that grows faster than the team answering it. None of that shows up as a broken page.

That is why store work here is split between the build and the desk behind it. A faster storefront on top of an unmanaged catalogue is a faster route to the same margin leak.

Ecommerce work, in practice

• Product data treated as an operational asset rather than a one-off import
• Returns and order exceptions worked to a written procedure
• Support hours matched to when customers actually buy

The website development page covers the build, and the ecommerce customer support guide covers the desk.

How this work usually starts

Ecommerce work starts with the catalogue and the queue rather than the storefront, because that is where the margin actually goes. The first month is normally spent making the current state visible — what is stale, what is late, what is being asked repeatedly — and the build follows the answer rather than preceding it.

Two numbers are worth agreeing before an ecommerce engagement starts: what a stale listing costs per week, and what a late return costs per case. Both are knowable, and together they usually justify the desk on their own.