OrderCore docs shell

Frequently Asked Questions

Short answers for onboarding and daily usage.

Start with docs Open support

If you are deciding whether to start, the docs path and FAQ now share the same product shell, spacing rhythm, and footer treatment.

Docs Canonical API and onboarding flow.

Support Operational help and setup escalation.

Tutorial Step-by-step first success path.

FAQ Short answers for common questions.

Do I need my own e-shop to start?

No. You can start with the guided API onboarding path, import a starter catalog, and add connectors only when required.

Is OrderCore a Shopify replacement?

No. OrderCore is the order backend and operations layer. Shopify can stay as the storefront while OrderCore Gateway syncs paid orders into a tenant-safe API workflow.

Is the Shopify app public?

Yes. OrderCore Gateway is listed on the Shopify App Store at apps.shopify.com/ordercore-gateway.

Do I need to change my Shopify storefront?

No. OrderCore Gateway is a backend sync layer for paid orders. Your Shopify theme, product pages, checkout configuration, and merchant workflow can stay in place while paid-order events are routed into OrderCore.

What happens if OrderCore is temporarily unavailable?

Shopify retries webhook delivery, and OrderCore uses idempotency to avoid duplicate orders when delivery is retried. The pilot validates this path before production use so support can confirm retry behavior and webhook visibility for your tenant.

Does this work with Shopify Markets and multi-store setups?

The gateway routes orders by shop and tenant, so multi-store and market-aware operations can be modeled in OrderCore. During onboarding we verify which shop domains, currencies, fulfillment locations, and downstream systems need to be included.

How do I authenticate requests?

Use X-API-Key or Authorization: Bearer header on each request.

How are duplicate order retries handled?

Use the Idempotency-Key header when creating orders.

What do I get from the 3-day assisted pilot?

The target outcome is one validated order path: API key, demo catalog, idempotent order creation, webhook readiness, a blocker list, and a clear go / no-go recommendation.

Do I need a card to create the first API order?

No. The first-order docs path is available before paid pilot checkout. Billing is for assisted setup, production handoff, and ongoing usage.

How do webhooks prove the integration is production-ready?

Each outbound delivery is signed, retried on retryable failures, and exposed through deliveries and metrics endpoints so support can see pending, failed, abandoned, and successful events.

Can I cancel billing myself?

Yes. Billing is Stripe-managed. The console exposes billing status and self-serve management when the tenant has an active billing portal URL.

What are default limits on Pro?

Current Pro limit is 50,000 API calls per month with usage headers in responses.

Where can I get setup help?

Use get started, the tutorial, or contact support@cloudpeakify.com.