Solutions · E-commerce & retail
We run our own stores - a Toronto coffee-equipment shop and a high-traffic electronics retailer - so we know exactly where the hours go. These are the systems we'd put into yours.
Sound familiar?
A third or more of your support volume is the same question with a different order number. Your team spends the day being a human tracking API.
WISMO tickets are the single highest-volume ticket type in e-commerce
Roughly 70% of carts never check out - and most stores send one templated email and move on. That's the cheapest revenue in your business, left on the table.
New products take ~25 minutes each to list properly, so descriptions lag, specs drift between channels, and stock levels lie.
33% of B2B online orders contained errors in 2025 industry surveys
At 20-30% of orders, every return means manual triage, labels, restocking decisions, and refund disputes - all by hand.
Price and stock fall out of sync between your store and marketplaces until an oversell - or a compliance strike - tells you.
Ads, COGS, shipping, and refunds live in five dashboards. True margin per SKU arrives weeks late, if it arrives at all.
What we'd build for you
01
A customer-facing agent connected to your actual orders: it answers WISMO instantly, handles address changes and return starts, and routes refunds above your threshold to a human approval queue.
The outcome
Most routine tickets resolved 24/7 - support headcount stays flat while orders grow.
02
Supplier sheets in, clean on-brand listings out - extracted, enriched, SEO'd, and pushed to every channel. A nightly agent diffs price, stock, and content across channels and flags drift. We classified 1,464 products on our own store this way.
The outcome
New SKUs live in minutes, and the catalog stops lying.
03
Every abandoned cart gets a personalized, multi-channel sequence - email, SMS, WhatsApp - and lapsed customers get win-back campaigns generated from what they actually bought.
The outcome
Recovering even 5-10% of abandoned carts is usually the cheapest revenue you'll add this year.
04
One morning message: yesterday's true contribution margin per SKU and channel, refund anomalies, ad-spend outliers, and stock-out risk 14 days ahead.
The outcome
You stop discovering margin problems a month late.
A note on doing this properly: Customer chat data is personal data - we build to GDPR/CCPA expectations, marketplace automations respect each platform's terms, and refunds above your threshold always require a human yes.
Why Peligent for this
Peligent started as an AI platform for WooCommerce - an 18-tool copilot with monitoring bots, used by real stores. Then we pointed it at our own: catalog AI, storefront chatbots, and sales dashboards running two real retail businesses today.
Read the e-commerce case study →A normal day on our own stores
07:10 catalog-ai ✓42 new SKUs enriched + published
09:32 support-bot ✓order status resolved, no human needed
12:04 channel-diff ✓price drift caught on 3 products
15:47 cart-recovery ✓abandoned cart converted - $214
23:58 margin-report ✓daily P&L compiled for the owner
Common questions
Every engagement starts with a fixed-price audit that maps your store and ends with exact numbers for the build - so you never commit blind. For most stores, support deflection and recovered carts pay for the system within months; we'll do that math with your numbers on the free discovery call.
Not if it's built properly. The agent is trained on your tone and policies, answers from your live order data, and escalates to a human the moment a conversation needs one. Refunds above your threshold always require a human approval - the bot never gives away money.
WooCommerce is our home turf - we built an AI platform and a WordPress.org plugin for it, and we run our own stores on it. The same architecture (catalog AI, support agents, recovery pipelines) works with Shopify and other platforms through their APIs.
On the free discovery call we'll tell you which of these pays for itself first in your store - catalog, support, recovery, or reporting.
No slides. No hype. 30 minutes.