E-commerceWoo & Dokan EngineeringCustom Software

A Multi-Channel
Import Engine for Vendors

Vendors needed their eBay, Amazon, Etsy and Shopify catalogues moved without retyping a listing. We built a WooCommerce and Dokan plugin that imports them, verifies vendors in three tiers, and runs on any marketplace.

Project SnapshotCovetable · AU
04
Sales Channels
eBay · Amazon · Etsy · Shopify
30+
Product Fields
Pricing · Media · Shipping
03
Verification
Phone · Address · Real ID
02
Delivery Phases
Core build · Added scope
Client
Joshua O’Driscoll · Covetable
Location
Australia
Platform
WooCommerceDokan
Engagement
Custom Extension Build
The Challenge

Catalogues Everywhere
Except Here

A marketplace competes for listings against platforms its sellers are already on. Asking them to retype an entire catalogue is the fastest way to lose them at signup.

Vendors arrived from eBay, Amazon and Etsy, each with its own product model, pricing and auction rules. Trust was missing both ways: buyers couldn't tell real traders from anonymous listings, and sellers couldn't see whether paid placements drove traffic.

What Was Breaking
  • Manual product entry blocking vendor onboarding, with no bulk path from existing channels
  • Three unrelated marketplace APIs, each with different auth, field names and price units
  • No way to signal seller legitimacy beyond Dokan’s default phone and address checks
  • Paid ad and featured-ad placements with no traffic feedback for the vendor
  • Re-imports risking duplicate listings and overwritten live products
Our Approach

A Dokan Extension,
Not a Fork

Built entirely as an extension plugin, so the marketplace keeps taking upstream Woo and Dokan updates. Where a default feature offered no hook, every core touch point was logged and handed over with the build.

01
Per-Vendor API Credentials

A REST API settings panel in the vendor dashboard where each seller connects their own eBay, Amazon, Etsy and Shopify accounts, with credentials scoped to the vendor and never shared marketplace-wide.

02
One Import Action, Four Sources

An import dropdown on the vendor product list pulls from any connected channel. Existing products are matched on title and price and skipped, so re-running an import never duplicates or overwrites a live listing.

03
Full Field Mapping, Including Auctions

Over thirty fields normalised per channel, from pricing, attributes, stock and shipping to auction reserves, bid increments and end dates where supported. Imports land as drafts so vendors review before publishing.

04
Three-Tier Vendor Verification

Real ID verification through Sumsub joins Dokan’s phone and address checks, with explicit consent, live status per tier, and tick or cross markers on the public store page. A dashboard prompt guides unverified vendors until all three tiers pass.

05
Extended Scope: Ad Analytics

Added after the core build, once sellers began paying for placement. Store visits and website clicks on ad and featured-ad listings are counted separately and published under the store name, so a seller can see what a placement actually returned.

Architecture

How the Pieces Connect

Channel APIs
01eBay Sell API
02Amazon SP-API
03Etsy Open API v3
04Shopify Admin API
Extension Plugin
Import & Verification Layer

Normalises each channel’s payload into one product model, de-duplicates on title and price, writes drafts, and drives verification state.

WooCommerceDokanPHPSumsub KYCWP-Cron
Marketplace Surfaces
01Vendor Dashboard
02Draft Product Queue
03Verified Store Badges
04Ad Analytics
The Outcome

Connecting,
Not Retyping

Vendors connect an account and review drafts instead of rebuilding a catalogue by hand, buyers get a visible trust signal, and the client keeps a plugin he can deploy anywhere.

Where It Landed
  • Bulk catalogue import shipped for eBay, Amazon and Etsy, with Shopify added in the second phase
  • Draft-first imports and title-plus-price matching keep live listings safe across repeat runs
  • Auction-specific fields carried across intact, so auction sellers are not second-class on the marketplace
  • Real ID verification live through Sumsub, surfaced as per-tier ticks on every store page
  • Separate store and website click counts published under the store name on ad and featured-ad listings, plus a portable plugin the client can deploy on any WooCommerce and Dokan marketplace
Engineering Note

Two requirements touched Dokan features with no extension hooks. We isolated those edits and shipped a change log with the plugin, so each core change can be re-applied or contributed upstream at the next update.

Stack

Technologies Used

WordPressWooCommerceDokanPHPMySQLWP REST APIeBay Sell APIAmazon SP-APIEtsy Open API v3Shopify Admin APISumsubWP-CronOAuth 2.0
More Work

Other Case Studies

RegistrationConsultationProsthetics
Single Source
The Client Record
StockFinanceKPI Board
Healthcare · Clinic Ops
From Paper Ledgers to a Clinic Platform
Six operational areas on one client record, from registration through to KPI dashboards.
Read case study
VacancyApplication
Authorise
Trainer Record
Quals
Reviews
SAML SSOMoodle Account
Education · Accreditation
A Trainer Management System Built on an HR Platform
A WordPress HR product extended into a trainer accreditation system with Moodle single sign-on.
Read case study
One Record
The Renovation Job
Tasks
Budget
CEOClientTrade
Real Estate · Project Ops
A Renovation Business Run From Four Dashboards
Four permission tiers and three role dashboards over one governed job record.
Read case study
Start a Conversation

Have a Project That Needsthe Same Treatment?

Tell us where the friction is. We’ll propose a clear place to start.

Start a ProjectBook a Call
What Happens Next
01
Share your brief

Send a project request or book a call. A written scope helps but isn’t required. NDA on request.

02
Reply in one business day

A project manager reviews your request and sets up a free call with a senior engineer.

03
Scope fixed and quoted up front

You get deliverables, timeline, and cost agreed before any work starts.