SVC-006 / eCommerce Development/ Cross-industry/ STATUS · ACTIVE

eCommerce Development for Restricted Markets.

Storefront platforms, crypto checkout, mirror failover infrastructure, and self-hosted analytics for restricted-market retailers across 18 verticals. White-hat ecommerce shops build on Shopify and a stable processor — a stack that gets AUP-banned in grey markets and costs the founder 90 days of revenue rebuilding from a cold start. We deploy on platforms that host the operator (WooCommerce, custom Next.js, Magento), plus the failover that keeps you online through domain seizures and processor freezes, plus the crypto checkout that lets buyers actually pay.

Get in touch
Service code
SVC-006
Coverage
18 verticals
Methodology steps
8
Build timeline
6-12 wk fresh · 4-8 wk migration
Platforms
WooCommerce · Next.js · Magento
Payments
USDT · BTC · XMR · alt processors
Engagement modes
Project · Retainer · Partnership
01Methodology8 sequential steps
  1. 01

    Site architecture audit

    Audit the current platform, performance baseline, security posture, payment integration, attribution stack, and failure modes. Most restricted-market retailers are running on a Shopify-alternative cobbled together with crypto plugins; we identify where the cracks already are and what the rebuild path looks like.

  2. 02

    Platform selection

    WooCommerce on managed VPS, custom Next.js storefront, Magento (Adobe Commerce) for catalogue-heavy operations, or alt-Shopify alternatives (CCBill-tolerant, OpenCart variants). Selection driven by catalogue depth, performance requirements, content-management needs, and the host's tolerance of the underlying category. We do not use Shopify itself — its acceptable-use policy bans most restricted categories at intake.

  3. 03

    Catalogue and PDP build

    Product structure tuned per category: compounds and stacks for steroids; strain libraries for cannabis; flavour-and-strength variants for vape and pouches; cycle-aware product relations for peptides. Schema markup tuned for ecommerce ranking on a category Google demotes by default. Bundle relationships and cross-sell logic baked into the catalogue.

  4. 04

    Crypto checkout integration

    USDT, USDC, BTC, XMR via specialised processors (NowPayments, BTCPay self-hosted, CoinPayments, Coinify). Settlement reconciliation, payment-window UX, multi-coin support, and confirmation flow all part of the build. Where mainstream-feeling rails are needed (Stripe-equivalent for adjacent products), we integrate alt-acquirers (Authorize.net high-risk, NMI, Soar).

  5. 05

    Mirror & failover infrastructure

    Standby domain on a different registrar, different host, different DNS, different jurisdiction where appropriate. Daily database sync, content mirror, and tested failover. When the primary domain takes a hit, the mirror is already ranking for the brand and ready to take traffic.

  6. 06

    Performance & scaling

    Server-side rendering or static generation where possible, CDN configuration (Cloudflare with bot management), image optimisation, caching tuned for the catalogue size. PageSpeed scores 85+ on PDPs as the standard, not the exception. Restricted-market sites get demoted twice — once for category, once for poor signals — so the technical baseline has to be high.

  7. 07

    Self-hosted analytics

    Plausible or Matomo on owned infrastructure. No Google Analytics — too much category-data exposure, plus reporting risk to a Google account that may not survive. Server-side conversion tracking for ad attribution. The analytics stack does not depend on Google or Meta tolerating the category.

  8. 08

    Documented runbook

    Runbook covering hosting, DNS, mirror activation, processor swap, and emergency-failover sequences. Operators know how to operate the infrastructure if we are not in the chat. Documentation lives outside Google Workspace; usually in a self-hosted Outline, BookStack, or Wiki.js instance under your account.

02Platforms & tacticsWhat we build on, and what we deliberately do not
StackWe doNotes
WooCommerce on managed VPSYesDefault for most catalogues. Mature ecosystem, deep customisation, host-tolerant.
Custom Next.js storefrontYesFor high-AOV operators with performance requirements. Higher build cost, better Core Web Vitals.
Magento (Adobe Commerce)YesFor catalogue-heavy operators (1000+ SKUs). Self-hosted only.
Headless commerceYesWhere front-end performance and back-end flexibility justify the build cost.
Crypto checkout (USDT, BTC, XMR)YesMultiple coin support. Self-hosted BTCPay where the operator wants full control.
Self-hosted analytics (Plausible, Matomo)YesNo Google Analytics. Privacy-respecting and category-data-safe.
Cloudflare proxy + bot managementYesCDN, DDoS protection, bot management. Standard layer.
ShopifyNoAUP bans most restricted categories. Shopify will close the store; payment processor will freeze. Non-starter.
BigCommerce, Wix, SquarespaceNoSame category-policy issues as Shopify, less mature alternatives in the restricted-friendly space.
Google Analytics 4NoCategory-data exposure plus dependency on a Google account that may not survive. Not worth the risk.
03Available for these industries18 verticals
IND-CAN

Cannabis & CBD eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-ADP

Adult Platforms eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-VAP

Vape & E-Cigarettes eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-PHM

Online Pharmacies eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-PEP

Peptides eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-SUP

High-Risk Supplements eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-AST

Anabolic Steroids eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-NOO

Nootropics eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-KRA

Kratom eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-PCH

Zins & Pouches eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-TOB

Tobacco eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-MUS

Magic Mushrooms eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-KLS

Ketamine & LSD eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-PTC

Psychedelic Therapy eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-EDR

Escort Directories eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-ADR

Adult Retail eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-GMC

Gentlemen’s Clubs eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

IND-FIN

Financial Services eCommerce

Platform build, crypto checkout, mirror failover — calibrated per vertical.

04DeliverablesDocumented at engagement
05eCommerce FAQAsked first
01Why not Shopify?

Shopify's acceptable-use policy bans most restricted categories — anabolic steroids, adult retail, kratom, vape, cannabis (depending on jurisdiction). The store will be closed within weeks of going live, and the payment processor freezes funds during review. Even with cloaking, Shopify resolves the issue inside one or two cycles. We do not build on platforms that will not host the operator.

02What platform do most restricted-market retailers use?

WooCommerce on managed VPS is the most common deployment. Mature ecosystem, deep customisation, host-tolerant when you choose a category-friendly hosting provider. For larger catalogues (1000+ SKUs), Magento. For high-AOV operators with performance requirements, custom Next.js storefronts.

03What if our domain gets seized?

The mirror domain is the failover. It runs on a different registrar (typically jurisdiction-different from the primary), different host, with daily database sync. Failover from primary-down to mirror-live is typically under 60 minutes including DNS propagation. The brand stays online; revenue resumes.

04Do you handle hosting?

We handle the hosting decision (registrar, VPS provider, jurisdiction, country-of-operation considerations). Operations can run under your account or ours; both work. The engagement identifies which fits your operational and compliance posture.

05Can you migrate us off our current platform?

Yes. Most migrations from a leaking Shopify-alternative or off-the-shelf builder take 4-8 weeks. SEO authority is preserved through structured 301 mapping and content migration. Cart and customer data migrates cleanly through standard ETL.

06What about product photography and brand creative?

Product photography stays with you. Creative direction, image treatment, and PDP layout we handle. Asset management and CDN configuration are part of the build. We do not photograph products; we make sure they look good once you have.

07Do you build the eCommerce platform under your name?

Either side. Some clients prefer the platform under their entity (operator-owned domain, registrar, host); some prefer ours managing the infrastructure. Both engagement models are supported. The engagement identifies which fits your category, jurisdiction, and risk posture.

08How does this work alongside your other services?

eCommerce Development is platform-side; SEO, Ads, Sales optimisation, and Content build on top of it. Most engagements run as a phased rollout: build the platform first, then layer the marketing services on top. Sometimes the engagement is platform-only; sometimes it is the bedrock of a full retainer.

06Engagement enquiryReply within 24h

Send a brief.

Reach out and we will scope. Or write directly: contacts@despitemarketing.com.

Encrypted in transit, read by a partner.