sales-bagisto
starsforks
How to install sales-bagisto?
sales-skills/sales/sales-bagisto
$npx -y skills add sales-skills/sales --skill sales-bagistoBagisto 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,
SKILL.md
| 1 | # Bagisto Platform Help |
| 2 | |
| 3 | ## Step 1 — Gather context |
| 4 | |
| 5 | If `references/learnings.md` exists, read it first for accumulated platform knowledge. |
| 6 | |
| 7 | Figure out what the user actually needs before diving in: |
| 8 | |
| 9 | - **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? |
| 10 | - **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? |
| 11 | - **Auth** — Laravel **Sanctum bearer token**, the **`X-STOREFRONT-KEY`** storefront key, a guest **cart token**, or **JWT** (legacy headless package)? |
| 12 | - **Hosting** — self-hosted (own infra: PHP/Laravel + MySQL/MariaDB + Redis) or **Bagisto Cloud** (managed)? |
| 13 | - **Version** — Bagisto 2.x line (current; v2.4.x as of mid-2026)? API packages need 2.3.0+. |
| 14 | |
| 15 | Skip-ahead rule: if the prompt already says what they need, go straight to Step 2. |
| 16 | |
| 17 | ## Step 2 — Route or answer directly |
| 18 | |
| 19 | If the question is really a cross-platform strategy, hand off with the exact command: |
| 20 | |
| 21 | | If the user wants… | Route to | |
| 22 | |---|---| |
| 23 | | Checkout conversion / order bumps / cart-abandonment tactics across carts | `/sales-checkout {question}` | |
| 24 | | Whether to use a Merchant of Record for global VAT/sales tax | `/sales-merchant-of-record {question}` | |
| 25 | | Digital-product pricing & launch strategy | `/sales-digital-products {question}` | |
| 26 | | Post-purchase email / abandoned-cart sequences | `/sales-email-marketing {question}` | |
| 27 | | Comparing Bagisto against another commerce backend | `/sales-checkout {question}` (platform selection) | |
| 28 | |
| 29 | Otherwise it's a Bagisto-specific question — answer it here. |
| 30 | |
| 31 | ## Step 3 — Bagisto platform reference |
| 32 | |
| 33 | **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 `references/bagisto-api-reference.md`. |
| 34 | |
| 35 | Answer using only the relevant section — don't dump the whole guide. |
| 36 | |
| 37 | ## Step 4 — Actionable guidance |
| 38 | |
| 39 | - **Pick the right auth for the surface.** The current unified API uses a public **`X-STOREFRONT-KEY`** (`pk_storefront_...`, generated at install or via `php artisan bagisto-api:generate-key`) on every Shop call, plus a **Laravel Sanctum bearer token** (`Authorization: Bearer 1|...`) for customer/admin-scoped routes. Guests get a **cart token** (`POST /api/shop/cart-tokens`). The older standalone `bagisto/graphql-api` (Mobikul) package instead uses **JWT** + an `x-app-secret-key` header — don't mix the two. |
| 40 | - **Two API flavors, same engine.** REST (`/api/shop/...`, `/api/admin/...`) and GraphQL (`/api/graphql`, playground at `/api/graphiql`) both split into a public **Shop API** and a protected **Admin API**. Choose REST for simple CRUD/scripts, GraphQL when a headless storefront wants to request exactly the fields it needs. |
| 41 | - **There are no native outbound webhooks in core.** Bagisto is a Laravel app — to notify a CRM/warehouse on an order, react to the **Laravel event** (e.g. `checkout.order.save.after`) in a listener and `fetch()` out yourself, schedule a polling job against `/api/admin/orders`, or add a community webhook package. Don't expect a Shopify-style "webhooks" settings page. |
| 42 | - **Self-host is free; Cloud is for not running infra.** The engine is **MIT and free** with no per-sale fee. **Bagisto Cloud** (Starter / Pro) sells managed, scalable hosting (uptime SLA, backups, support) so you don't run the LAMP/Redis stack yourself. |
| 43 | |
| 44 | If you discover a gotcha or fix not in `references/learnings.md`, append it there with today's date. |
| 45 | |
| 46 | ## Gotchas |
| 47 | |
| 48 | *Best-effort from research (2026-0 |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
