Multichannel Sync

v1.0.0

Plan inventory, pricing, and listing synchronization across multiple sales channels to prevent overselling, maintain consistent branding, and optimize channe...

0· 111·0 current·0 all-time
byLeroyCreates@leooooooow

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for leooooooow/multichannel-sync.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Multichannel Sync" (leooooooow/multichannel-sync) from ClawHub.
Skill page: https://clawhub.ai/leooooooow/multichannel-sync
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install multichannel-sync

ClawHub CLI

Package manager switcher

npx clawhub@latest install multichannel-sync
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (multichannel inventory/pricing/listing plan) aligns with the SKILL.md: the skill produces a playbook and matrices and explicitly states it does not integrate with APIs. There are no unexpected binaries, env vars, or config paths requested.
Instruction Scope
The runtime instructions ask for seller-provided business data (channels, inventory structure, pricing rules, etc.) and produce a plan. They do not instruct the agent to read local files, system state, or external credentials, nor to transmit data to third-party endpoints.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes filesystem and network install risks.
Credentials
The skill declares no required environment variables, credentials, or config paths. The requested inputs are business data (inventory, pricing, SKUs) appropriate to a planning playbook.
Persistence & Privilege
always is false and the skill does not request elevation or to modify other skills or system settings. It may be invoked autonomously per platform defaults, which is expected for skills and not raised as a concern here.
Assessment
This skill is a planning playbook only — it won't connect to your systems by itself. Before using: (1) avoid pasting secrets or API keys into the input fields (the output is plain text and may be stored); (2) verify any marketplace policy recommendations it gives against the current vendor docs and get legal review for MAP/distributor issues; (3) if you later adapt the plan into automation that calls APIs or syncs inventory, ensure that integration code only uses minimal, scoped credentials and follows least privilege; (4) if you allow autonomous agent actions on your account, treat that as a separate risk assessment — this skill by itself does not request credentials or perform network actions.

Like a lobster shell, security has layers — review code before you run it.

latestvk9788vybrwznj5wv1399km9qa18589m1
111downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Multichannel Sync

Selling on Shopify plus Amazon plus TikTok Shop plus one or two regional marketplaces sounds great until two customers buy the last unit at the same time, or Amazon suppresses your Buy Box because a 10% TikTok flash sale violated their fair pricing policy. Multichannel Sync gives you a concrete playbook for keeping stock counts, prices, and listing data aligned across channels without breaking any individual platform's rules.

Use when

  • A seller says "I'm overselling on Amazon every time TikTok Shop runs a promotion — how do I set up inventory buffers and sync rules that stop this?"
  • A brand is adding a third or fourth channel and needs a decision framework for whether to run them off a single inventory pool or split stock by channel.
  • A founder asks "Amazon just warned me about fair pricing — can you audit my cross-channel pricing and tell me what to fix?"
  • An operations lead is evaluating inventory and listing sync tools (ChannelAdvisor, Sellbrite, Linnworks, Zentail) and wants a requirements checklist before committing to one.

What this skill does

Produces a multichannel synchronization plan covering three layers: inventory (which channels share a pool, which carry reserved buffers, how low-stock thresholds throttle listings before a stockout), pricing (which channel is the anchor price, what differential each secondary channel is allowed to deviate, and how promotions cascade without triggering marketplace parity penalties), and listing content (which fields must be identical, which should vary by platform for SEO or policy reasons, and how to propagate updates). It also outlines the reconciliation cadence, exception handling workflow, and the specific platform rules you must respect on each marketplace.

Inputs required

  • Channel list (required): every channel you sell on, including direct storefront, marketplaces, and any B2B portals, with monthly order volume for each.
  • Current inventory structure (required): whether stock is centralized in one location, split by channel, or managed across multiple 3PLs; include safety stock and typical replenishment lead time.
  • Pricing strategy (required): anchor price by SKU, any MAP or MSRP policies, and any known parity constraints from Amazon, Walmart, or other marketplaces.
  • SKU variation rules (required): which products have parent-child or variant structures, and any channel-specific SKU or listing ID mappings you already use.
  • Integration stack (optional): current OMS, ERP, or listing tool and any known sync frequency or reliability issues.
  • Promotion calendar (optional): upcoming sitewide or channel-specific sales so the plan can pre-define safe discount ranges and buffer stock.
  • Category risk factors (optional): perishables, hazmat, oversize, or other restrictions that affect where inventory can legally sit.

Output format

A three-section sync playbook. Section one is an inventory sync matrix showing each channel's stock pool, buffer percentage, low-stock throttle threshold, and what happens when inventory drops below the safety line. Section two is a pricing matrix with anchor, allowed deviation, cascade rules for promotions, and a short explanation of each marketplace's parity or fair-pricing policy you must respect. Section three is a listing content playbook specifying which fields are shared, which vary, and the push order when something changes. A closing checklist lists the top oversell, price-parity, and listing-suppression risks with the monitoring alert each one needs.

Scope

  • Designed for: ecommerce operations leads, multi-channel sellers, and brand managers coordinating across marketplaces and direct storefronts.
  • Platform context: Shopify, Amazon, Walmart, TikTok Shop, Shopee, Lazada, eBay. Additional marketplaces can be accommodated with generic rules.
  • Language: English.

Limitations

  • Does not integrate directly with ERP, OMS, or channel APIs; the output is a plan you implement in your existing tooling.
  • Marketplace rules change frequently — the plan reflects typical policy structures, but you should verify current terms with each platform.
  • Does not replace legal review of MAP agreements, distributor contracts, or cross-border tax obligations.

Comments

Loading comments...