vertical-retail

Featured

Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder and cart recovery), the must-model entities (Product→Variants matrix, channel-aware InventoryLevel, ReorderRule, PricingRule, AbandonedCart), and what a naive build gets wrong (no variant model, single-channel inventory, reorder without lead-time/safety-stock). Applied by architect/pm during spec authoring so they aren't naive about retail; checked implicitly by pci-reviewer + cms-reviewer.

AI & Automation 92 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
66
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Retail & e-commerce — spec it like someone who's run a store The SMB retail buyer already pays Shopify ($39–399/mo + 2.9%), BigCommerce, Wix, Ecwid, or WooCommerce. They are not naive — so the spec can't be either. A storefront that "has products and a cart" is table stakes; the value is in the parts those platforms do badly. Read this before writing the catalog/inventory/pricing/cart sections of any retail ARCH or PLAN doc. ## 1. Domain vocabulary (use these exact words) - **SKU vs variant** — a **variant** is one buyable configuration (Red / Large); its **SKU** is the unique code that variant ships and is counted under. A "product" is the parent; you stock, price, and sell *variants*, not products. - **Multichannel / omnichannel** — selling across several channels (own storefront, Amazon, eBay, in-store POS, Instagram). *Omnichannel* additionally means one inventory pool behind all of them. Channel-awareness is the whole game for SMB inventory. - **Reorder point** — stock level that triggers a purchase order = (avg daily demand × **lead time** in days) + **safety stock**. **Lead time** = supplier days from order to receipt. **Safety stock** = buffer for demand/lead-time variance. Reordering without all three is wrong. - **COGS** (cost of goods sold) and **margin** = (price − COGS) / price. **Landed cost** = unit cost + freight + duties + handling; margin must use landed cost, not invoice cost. - **ATS / available to sell** = on-hand − allocated (reserved ...

Details

Author
avelikiy
Repository
avelikiy/great_cto
Created
5 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

vertical-logistics

Domain knowledge for the logistics & supply-chain vertical (SMB shipping & inventory) so architect and pm don't spec naively. Covers the vocabulary (TMS vs WMS, multi-carrier rate shopping, dimensional weight, BOL/ASN, lot/batch, reorder point), the non-obvious rules incumbents get right, what a naive build gets wrong, and the entities each of the four products (shipment-tracking, warehouse-lite, route-optimization, po-mgmt) must model. Applied by architect when writing ARCH-{slug}.md and by pm when writing PLAN-{slug}.md for any logistics product.

92 Updated today
avelikiy
Code & Development Featured

vertical-restaurants

Domain-knowledge primer for the restaurants & hospitality vertical (dine-in, pickup, delivery). Gives architect and pm the vocabulary, non-obvious operating rules, must-model entities, and incumbent landscape so a restaurant-product spec isn't naive about modifiers, 86'd items, aggregator commissions, tip law, and razor-thin margins. Covers the 4 products: online-ordering, reservations, loyalty, shift-scheduling.

92 Updated today
avelikiy
Web & Frontend Listed

store-design

Design and build a store, product page, landing page or checkout that sells — deciding which selling mechanics belong on THIS merchant's product rather than pasting a template. Reads the product (one item or a catalogue, impulse or considered, physical or digital, consumable or durable, variants, expiry) and deduces which sections to lay and in what order, each with its reason. Carries quantity breaks (a radio group of named tiers, never a quantity stepper), the free-shipping threshold bar, the order bump (never pre-ticked), the sticky mobile add-to-cart, email capture, the buy box order, and proof that is never fabricated. Use for any product page, landing page, cart, checkout, upsell, bundle, volume discount, tiered pricing, average order value or AOV work, for Shopify sections, and whenever a generated storefront looks fine but sells nothing. Carries the EU rules on pre-ticked add-ons (Article 22, Directive 2011/83/EU) and on struck-through prices.

0 Updated 1 weeks ago
kinerette