Shopify
CORE STORE
· POD integrations and supplier migration
Keep your listings.
Keep existing listings live while moving supported store fulfillment to CKF. Connect your store, prepare each design in CKF, bind every variant, and sync new orders after connection.
Orders containing an unbound variant enter Pending status. They cannot be paid or sent to production until the CKF design and variant binding are completed.
WOO
CORE STORE
TIKTOK
CORE STORE
Etsy
CORE STORE
WIX
CORE STORE
CKF API
CORE STORE
Built for existing POD stores changing or adding fulfillment
Keep listings
Rebind variants
Control order sync
FOR STORES THAT ARE ALREADY SELLING
Change fulfillment without rebuilding the storefront.
This page is for POD sellers with live listings, variants, traffic, or orders who want to add CKF, replace an existing fulfillment provider, or control the transition without republishing the catalog.
GROWTH-STAGE SELLERS
Add CKF without republishing products
Connect the active store, keep current listings live, and prepare CKF design and variant bindings before moving fulfillment.
Existing listings stay published
Every variant can be mapped
New orders sync after connection
SUPPLIER SWITCH
Keep the storefront, change the fulfiller
Reconnect the fulfillment relationship inside the supported store integration instead of moving the catalog through a separate migration system.
Recreate or upload the CKF design
Bind each store variant to CKF
Pay and produce after binding
CUTOVER CONTROL
Decide which orders CKF should receive
Keep one fulfillment provider active for each product to reduce duplicate fulfillment risk. Use the available sync control if orders from products not published through CKF should remain paused.
One active fulfiller recommended
Non-CKF product order-sync control
Pending orders remain visible
SUPPORTED SALES-CHANNEL CONNECTIONS
Use the same store. Reassign fulfillment to CKF.
Supplier migration is available through supported CKF store integrations. Existing products do not need to be republished: connect the channel, recreate or upload the CKF design, bind every store variant, and let new post-connection orders sync to CKF. Product eligibility, status updates, and tracking behavior can still vary by platform.
Marketplace channels
Owned storefronts
AVAILABLE
Shopify
Use CKF' s Shopify integration for activestores that need stronger catalog control,automation, and multi-store operations.
Bulk publishing and SKU mapping
Multi-store synchronization
Shopify Flow,webhooks, status, and，tracking updates
AVAILABLE
WooCommerce
Connect a WooCommerce store and moveeligible print-on-demand orders into CKFproduction and delivery.
Connect an existing self-hosted storefront
Confirm SKU, variation, and order mapping
Use CKF fulfillment without changing thesales channel
AVAILABLE
Wix
Connect Wix to create and publish eligible CKF products, then use the confirmed production, packing, and direct-to-customer shipping workflow.
Choose eligible CKF products
Prepare designs and configure productoptions
Check content, variants, pricing, andstorefront display before publishing
SUPPLIER MIGRATION INSIDE THE STORE INTEGRATION
Keep listings live. Rebuild the fulfillment binding.
The store and its products remain in place. The migration work happens in CKF by reconnecting each existing store variant to a CKF design and product variant.
1
Connect the existing store
Add the supported sales channel to CKF. Existing storefront products remain published.
2
Prepare the CKF design
Recreate or upload the design in CKF for the product that CKF will fulfill.
3
Bind every variant
Map each existing store variant to the matching CKF product variant and design.
4
Receive new orders
Orders created after the integration is connected can sync to CKF.
5
Pay and fulfill
Bound orders can be paid and released to CKF production and fulfillment.
Pending / Bind / Pay / Produce
If any ordered variant is not yet bound, the order enters Pending status and cannot be paid or produced. Complete the CKF design and variant binding first. To reduce duplicate fulfillment risk, keep one fulfiller active per product or pause synchronization for orders from products not published through CKF.
DEVELOPER INTEGRATION
Use documented CKF endpoints for custom workflows.
The CKF API is a separate developer option, not a required supplier-migration route for supported store integrations. Published documentation covers authentication, product and design data, order creation and queries, and tracking queries. Confirm endpoint, field, error-handling, and implementation scope before development.
Authentication
Access Token in the published documentation
Catalog data
Design List, Product List, Product Detail, and API/CSV Products
Order operations
Order creation, order list, and order-detail workflows
Tracking queries
Tracking-number and shipment-information queries
THREE OPERATING SCENARIOS
Choose the setup that matches the store.
Use the supported store integration for both new CKF products and existing listings changing suppliers. Use the API only when a separate custom system must work with the published endpoints.
NEW CKF PRODUCTS
For stores adding new products
Use the selected platform integration to prepare eligible CKF products and connect the supported order workflow.
· Eligible product selection
· CKF design preparation
· Platform-specific workflow confirmation
SUPPLIER MIGRATION
For existing listings changing fulfillment
Keep the products published, connect the store to CKF, recreate or upload the design, and bind every existing variant to the matching CKF product variant.
· No product republishing
· New post-connection orders sync
· Unbound orders remain Pending
FOR COMPLEX
OPERATIONS
OPERATIONS
CKF API
For workflows beyond the native connection
Assess whether the current CKF endpoints, fields, authentication, and implementation support cover the proposed storefront or internal operating workflow.
· Endpoint and field review
· Authentication and error handling
· Technical implementation confirmation
OPERATIONAL QUESTIONS
Questions established sellers ask before connecting.
No. Existing storefront products can remain published. Connect the supported store integration to CKF, thenrecreate or upload the design and bind every existing store variant to the matching CKF product variant.
New orders created after the integration is connected can sync to CKF. This supplier-migration workflow is available across supported CKF store integrations.
The order enters Pending status and cannot be paid or sent to production. Complete the CKF design and variant binding first; the order can then be paid and released for production and fulfillment.
CKF recommends keeping only one fulfillment provider active for each product. If you are not ready to sendorders from products that were not published through CKF, use the available order-sync control to pause those orders.
No. Supplier migration is supported across CKF store integrations, but product eligibility, personalization,publishing behavior, status updates, and tracking behavior may differ by platform. Confirm the selected productand platform workflow before launch.
Use the CKF APl when the published authentication, product, order, and tracking-query endpoints cover aseparate custom development requirement. The APl is not required to migrate existing listings through asupported store integration. Confirm endpoint and field coverage before development.
Customers can participate in the whole process of product design and manufacturing, to meet the personalized needs of the one-stop design platform.
Copyright © 2026 CatKissFish ICP No.2021011063-1
$240 OFF
For New
Work Orders
Help center