Skip to content
Skills Library
Programming · Tool integration

b2c-scapi-admin

/b2c-scapi-admin

Build backend integrations that sync data between B2C Commerce and external systems like ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs. Use this skill whenever the user needs to pull or push orders, products, inventory, or customer data programmatically from a backend service, set up server-to-server authentication with Account Manager client credentials and admin OAuth scopes, implement bulk inventory imports with NDJSON, or call any Commerce API from a script or pipeline (not a storefront). Also use when building nightly data exports, warehouse sync jobs, or customer data integrations — eve

Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Build backend integrations that sync data between B2C Commerce and external systems like ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs. Use this skill whenever the user needs to pull or push orders, products, inventory, or customer data programmatically from a backend service, set up server-to-server authentication with Account Manager client credentials and admin OAuth scopes, implement bulk inventory imports with NDJSON, or call any Commerce API from a script or pipeline (not a storefront). Also use when building nightly data exports, warehouse sync jobs, or customer data integrations — eve

Original author description

Build backend integrations that sync data between B2C Commerce and external systems like ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs. Use this skill whenever the user needs to pull or push orders, products, inventory, or customer data programmatically from a backend service, set up server-to-server authentication with Account Manager client credentials and admin OAuth scopes, implement bulk inventory imports with NDJSON, or call any Commerce API from a script or pipeline (not a storefront). Also use when building nightly data exports, warehouse sync jobs, or customer data integrations — eve

How it works

  1. Tool choice
  2. Execute deliberately
  3. Conditional references
Original SKILL.md headings · 50 lines, 335 words
SKILL.md preview
---
name: b2c-scapi-admin
description: Build backend integrations that sync data between B2C Commerce and external systems like ERPs, OMS, WMS, or CRMs using SCAPI Admin APIs. Use this skill whenever the user needs to pull or push orders, products, inventory, or customer data programmatically from a backend service, set up server-to-server authentication with Account Manager client credentials and admin OAuth scopes, implement bulk inventory imports with NDJSON, or call any Commerce API from a script or pipeline (not a storefront). Also use when building nightly data exports, warehouse sync jobs, or customer data integrations — even if they just say "pull orders into our ERP" or "sync inventory from the warehouse".
---

# SCAPI Admin APIs

Build backend integrations or manage Commerce data through standard Admin APIs.
Use the `b2c-scapi-shopper` skill for storefront flows.

## Tool choice

When B2C MCP is available:
- Prefer a dedicated task tool. Otherwise read `skill://mcp/b2c-mcp-scapi/SKILL.md` once
  through resources or `skills_read`, then use `skillRead: true`.
- `scapi_search`: bundled standard contracts, offline. Find method/path/operationId,
  then inspect selected parameters, fields, and security scopes. Return compact projections.
- `scapi_execute`: supported Admin JSON operations with configured Account Manager
  auth and automatic operation/tenant scopes. Use `config_inspect` with masking;
  do not fetch or print tokens manually for these calls.
- `scapi_schemas_list`: live tenant schemas, including custom attributes and APIs.
  `scapi_custom_apis_get_status`: custom registration. Custom execution and binary
  transfers are unsupported by code mode; use an appropriate integration client.
- `docs_search`/`docs_read`: platform semantics, limits, and auth setup. No duplicate
  docs lookup is needed merely to repeat a discovered contract.

For CLI/integration development: `b2c scapi schemas list` and
`b2c scapi schemas get <family> <name> <version>` retrieve live contracts.
Read [integration examples](references/CLIENT-EXAMPLES.md) only when implementing
an external client, token flow, or bulk import. There is no CLI code-mode equivalent.

## Execute deliberately

- Use configured short code, tenant, and site values. Admin auth requires an
  Account Manager client, API grants, and `SALESFORCE_COMMERCE_API:<tenant_id>`.
  SLAS credentials do not replace Admin credentials.
- Inspect the operation before use; examples are illustrative. For tenant-specific
  fields use live schemas. Check official docs for version-specific semantics.
- Distinguish creation from update; PUT may do both. Verify existence and intent,
  then read back meaningful fields. Check earlier writes before retrying a failure.
- Page/filter at the API and return IDs, selected fields, totals/hasMore, and errors.
  Do not emit whole response trees or log credentials.
- Safety is method-based: POST searches can require a targeted allow rule.
  Confirmation-required code-mode requests stop; do not bypass them.

## Conditional references

- [OAuth scopes](references/OAUTH-SCOPES.md): integration grants; compare with the operation's security.
- [Integration patterns](references/INTEGRATION-PATTERNS.md): ETL, sync, bulk import.
- `b2c-config` skill: CLI credentials and precedence.
- Official docs: `commerce-api/authorization-for-admin-apis`, `commerce-api/auth-z-scope-catalog`,
  `commerce-api/timeouts-limits`, `commerce-api/throttle-rates`,
  `commerce-api/inventory-impex-best-practices`.
Files in this package (5)
  • SKILL.md 3 KB
  • evals/trigger-evals.json 2 KB
  • references/CLIENT-EXAMPLES.md 13 KB
  • references/INTEGRATION-PATTERNS.md 15 KB
  • references/OAUTH-SCOPES.md 10 KB

Versions

The database has no other skills named b2c-scapi-admin.

Database snapshot: 13.11.2026 · package version 8158afbfe467 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95erupt-admin
    一句话生成数据管理后台。当用户描述想要一个管理系统、后台、CRUD 系统、信息管理平台,或各类业务系统如 CRM(客户管理)、ERP、OA、进销存、库存管理(WMS)、订单管理(OMS)、会员管理、人事管理(HR)、CMS 内容管理、工单系统、报名/预约系统(如"生成一个图书管理后台"、"做一个 CRM"、"搭个进销存"),或要求为已生成的 erupt 项目增改功能时使用。Generate a full admin backend from one sentence — use when the user asks for an admin…
  • 100sf-b2c-scapi
    Build with Salesforce Commerce API (SCAPI) — Shopper APIs (Products, Search, Baskets, Orders, Customers), SLAS authentication, Commerce SDK for Node.js, rate limiting, pagination, and headless commerce patterns. This is the primary B2C API. Use when building headless storefronts or API integrations.
  • 100b2c-scapi-shopper
    Call Shopper Commerce APIs (SCAPI) from headless storefronts and composable commerce apps. Use this skill whenever the user is building with PWA Kit, Storefront Next (SFNext), or a headless frontend and needs to search products, manage baskets, submit orders, access customer…
  • 100api-client-development
    Creating typed API clients with OpenAPI specs, authentication, and OAuth scopes for SCAPI and similar APIs. Use when adding a new SCAPI client, generating types from an OpenAPI spec, setting up OAuth middleware, or integrating a new Commerce API endpoint.
  • 100node-backend
    Build Node.js backends for Salesforce Commerce — SFCC server-side JavaScript (not actual Node.js runtime), PWA Kit backend (Express-like SSR server), Commerce SDK for server-side SCAPI access, and async patterns for external service integration. Use when building server-side commerce logic.
  • 100tiendanube-erp-integration
    Apply when connecting an ERP, OMS, WMS or PIM to a Tiendanube / Nuvemshop store, or when migrating catalog and customers from another platform: the official ERP guide (authentication, API usage, catalog, inventory and locations, orders, order editing, invoices, labels,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.