| name | sales-bagisto |
| description | 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). |
| argument-hint | [describe what you need help with in Bagisto — e.g. 'pull all orders into my warehouse via the REST API' or 'Sanctum vs storefront-key auth'] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","checkout","ecommerce","platform"] |
| github | https://github.com/bagisto/bagisto |
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-purchase email / abandoned-cart sequences | /sales-email-marketing {question} |
| Comparing Bagisto against another commerce backend | /sales-checkout {question} (platform selection) |
Otherwise it's a Bagisto-specific question — answer it here.
Step 3 — Bagisto platform reference
Read references/platform-guide.md for the full reference — modules and what's API vs event vs UI-only, pricing/plan posture, data model with JSON shapes, and quick-start recipes. For raw auth/endpoint/pagination detail, read .
