sales-bagistolisted

Bagisto platform help — open-source (MIT) Laravel/PHP eCommerce framework for developers and makers: products, orders, carts, customers, and checkout via a REST API and a GraphQL API (Shop + Admin), plus multi-vendor marketplace, POS, B2B, and multi-channel/headless storefronts, self-hosted or on Bagisto Cloud. Use when building a Bagisto REST or GraphQL integration, authenticating requests (Laravel Sanctum bearer token, X-STOREFRONT-KEY storefront key, or JWT for the headless package), creating a guest cart token, pulling products/orders into a CRM or warehouse, fixing a broken install or slow page loads, fixing broken images after an APP_URL change, choosing self-host vs Bagisto Cloud, or comparing Bagisto to Medusa/Saleor/Shopify. Do NOT use for cross-cart checkout-conversion strategy (use /sales-checkout) or picking a Merchant of Record for global tax (use /sales-merchant-of-record).
sales-skills/sales · ★ 96 · API & Backend · score 76

Install: claude install-skill sales-skills/sales

# Bagisto Platform Help ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated platform knowledge. Figure out what the user actually needs before diving in: - **Goal** — building/debugging an API integration, syncing orders/products to a CRM or warehouse, a checkout/conversion question, an install/ops problem, or a platform-selection decision? - **Surface** — REST API (`/api/shop`, `/api/admin`), GraphQL API (`/api/graphql`), the older headless `bagisto/graphql-api` package (`/graphql`), the admin panel UI, or a marketplace/POS add-on? - **Auth** — Laravel **Sanctum bearer token**, the **`X-STOREFRONT-KEY`** storefront key, a guest **cart token**, or **JWT** (legacy headless package)? - **Hosting** — self-hosted (own infra: PHP/Laravel + MySQL/MariaDB + Redis) or **Bagisto Cloud** (managed)? - **Version** — Bagisto 2.x line (current; v2.4.x as of mid-2026)? API packages need 2.3.0+. Skip-ahead rule: if the prompt already says what they need, go straight to Step 2. ## Step 2 — Route or answer directly If the question is really a cross-platform strategy, hand off with the exact command: | If the user wants… | Route to | |---|---| | Checkout conversion / order bumps / cart-abandonment tactics across carts | `/sales-checkout {question}` | | Whether to use a Merchant of Record for global VAT/sales tax | `/sales-merchant-of-record {question}` | | Digital-product pricing & launch strategy | `/sales-digital-products {question}` | | Post-