Skip to main content

Ecommerce integration services

Send personalised orders straight to your POD supplier

We connect your Cmsmart Ecommerce or WooCommerce store to a print-on-demand or fulfilment provider through its API. Each paid order line goes to the supplier with its own print-ready file, print area and variant, and tracking returns to the store. It is built as custom development and quoted after a free assessment.

Book a free integration assessment How we run projects

Quoted per project, no obligation. The assessment is free and carries no price list.Updated

WooCommerce order screen with the preflight panel and a print-ready file
The print-ready file on the order line is what an integration sends to the supplier. Demo store, sample products and prices.

The short answer

Built on WooCommerce. The design, the print-ready file and the order reach your fulfilment provider without re-keying, and tracking comes back to the store.

Key facts
ScopePaid orders, per-line print files, variant mapping, supplier routing, status and tracking back
What syncsOrder and file to the supplier; production status and tracking to WooCommerce and the customer email
Typical inputsSupplier account or sandbox, API key, product and variant list, your print areas, example orders
DeliverablesData map, the bridge on staging, tested orders, routing rules, monitoring and a run book
How pricing worksFree assessment, then a quote per project paid by milestone. Supplier fees are paid to the supplier.

Data flow

How the data moves

Personalised order to POD supplierThe shopper designs in the Cmsmart designer. Each order line keeps its own design and print-ready file. The integration layer maps variants, can route by product or region, sends the order and file to the supplier API, and brings tracking back to WooCommerce.Shopper designs1Cmsmart designer2WooCommerce order3Print-ready file4Integration layer5Supplier API6Production7Tracking to store8Route by product or regionSupplier ASupplier BPersonalised order to POD supplierThe shopper designs in the Cmsmart designer. Each order line keeps its own design and print-ready file. The integration layer maps variants, can route by product or region, sends the order and file to the supplier API, and brings tracking back to WooCommerce.Shopper designs1Cmsmart designer2WooCommerce order3Print-ready file4Integration layer5Supplier API6Production7Tracking to store8Route by product or regionSupplier ASupplier B
Personalised order to POD supplier. The shopper designs in the Cmsmart designer. Each order line keeps its own design and print-ready file. The integration layer maps variants, can route by product or region, sends the order and file to the supplier API, and brings tracking back to WooCommerce.

The problem

What does manual re-sending of print files cost?

  • Files downloaded from wp-admin and uploaded to the supplier by hand
  • A supplier plugin that syncs catalogue items but not the shopper's own design
  • Orders for one product that should go to different suppliers by country or cost
  • No tracking on the store, so customers write to ask
  • Errors found after production instead of before

What syncs

What moves, which way, and when

DataDirectionSystem of recordTriggerNotes
Paid order Store to supplier WooCommerce On payment (webhook) Shipping address, items, variant mapping
Print file Store to supplier Cmsmart designer With the order One print-ready file per line, per print area
Order accepted or rejected Supplier to store Supplier Webhook or polling Rejections raise an alert
Production status Supplier to store Supplier Webhook or polling Shown in My Account
Tracking number and URL Supplier to store Supplier Webhook or polling Added to the order and the customer email
Routing rule Store Cmsmart Per order By product, region or cost, if you use more than one supplier

Typical defaults. The final directions, triggers and frequency are set in the assessment.

Fulfilment providers

Fulfilment providers we connect to

One section per provider, with an anchor. Facts about a provider carry their source and the date we read it (10 October 2026). Where a provider's documentation could not be read, the section says "via the provider's API" and nothing more.

Printful

What it fulfils
A print-on-demand and dropshipping service.
How orders and files pass
Its API documents creating an order, with print files given by URL and a file type per placement, a file library, your own external ID so a retried request cannot duplicate an order, and webhooks.
The standard plugin
Check Printful's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Printful's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Printful, Printful API documentation (read 10 October 2026).

Printful integration →

Printify

What it fulfils
A print-on-demand platform where designs are put on its product catalogue.
How orders and files pass
Its API documents orders, per-variant print areas on products, your own external ID on a line item, and webhooks.
The standard plugin
Check Printify's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Printify's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Printify, Printify API documentation (read 10 October 2026).

Printify integration →

Gelato

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Gelato's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Gelato's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Its public documentation could not be read on 10 October 2026, so nothing more is stated here.

Gelato integration →

Gooten

What it fulfils
A print-on-demand service for products such as fashion, home decor and drinkware.
How orders and files pass
Its order API takes a list of images per item, each with the URL of a publicly accessible image, and a source ID for your own order reference.
The standard plugin
Check Gooten's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Gooten's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Gooten, Gooten: submitting an order (read 10 October 2026).

Prodigi

What it fulfils
A print-on-demand platform with a print API.
How orders and files pass
Its order items carry assets with a print area and a URL, with a callback URL and an idempotency key on the order.
The standard plugin
Check Prodigi's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Prodigi's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Prodigi, Prodigi Print API reference (read 10 October 2026).

CustomCat

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Its API accepts a catalogue SKU with an external design URL, which must be directly downloadable as PNG or JPG. The bridge must therefore supply a file in that format, which we confirm in the data map.
The standard plugin
Check CustomCat's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to CustomCat's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: CustomCat API getting started (read 10 October 2026).

SPOD (Spreadconnect)

What it fulfils
A service for selling print-on-demand apparel through integrations. The SPOD site currently presents Spreadconnect.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check SPOD (Spreadconnect)'s current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to SPOD (Spreadconnect)'s products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: SPOD (page shows Spreadconnect) (read 10 October 2026).

T-Pop

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check T-Pop's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to T-Pop's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Its public documentation could not be read on 10 October 2026, so nothing more is stated here.

Teelaunch

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Teelaunch's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Teelaunch's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Its public documentation could not be read on 10 October 2026, so nothing more is stated here.

Apliiq

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Apliiq's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Apliiq's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Its public documentation could not be read on 10 October 2026, so nothing more is stated here.

Lulu Direct

What it fulfils
Print-on-demand for books. Lulu's developer portal offers a print API with sandbox and production.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Lulu Direct's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Lulu Direct's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Lulu developer portal (read 10 October 2026).

Peecho

What it fulfils
A print-on-demand service for photo books with an API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Peecho's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Peecho's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Peecho (read 10 October 2026).

Printed Mint

What it fulfils
A print and fulfilment provider. We connect to it via the provider's API.
How orders and files pass
Via the provider's API. The order and file format are confirmed against its current documentation in the assessment.
The standard plugin
Check Printed Mint's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Printed Mint's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Its public documentation could not be read on 10 October 2026, so nothing more is stated here.

Scalable Press

What it fulfils
A custom apparel printing and fulfilment service.
How orders and files pass
Its API works with quotes: a standard quote covers one design on one or more products shipped to one address, and bulk quotes cover more varied orders.
The standard plugin
Check Scalable Press's current plugin documentation for a shopper's own personalised file on each order line. Where it is not covered, the bridge uses the API.
The Cmsmart bridge
The print-ready file of each line, mapped to Scalable Press's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Source: Scalable Press, Scalable Press API documentation (read 10 October 2026).

Your own print partner or local printer

What it fulfils
A printer you already work with, in your country or region.
How orders and files pass
If it has no API, the order goes by SFTP file drop, a scheduled CSV or an email order sheet with the print-ready file attached. This is less real-time than an API, and the assessment states the limits.
The standard plugin
Not applicable: there is no off-the-shelf plugin for a private arrangement, so the bridge is the integration.
The Cmsmart bridge
The print-ready file of each line, mapped to your partner's products, sent with the order. Status and tracking return to WooCommerce, and orders can be routed to another supplier by product or region.

Approach

Connector, integration platform or custom code

The free assessment compares the three on fit, cost driver and limits, and tells you which one we would pick and why.

  • A. Marketplace connector

    A licence from the WooCommerce Marketplace or the system's own app store, configured for you.

    Fits: Standard flows and a well-supported system.

    Limits: Limited to what the connector exposes; fees are paid to its vendor.

  • B. Integration platform

    A hosted integration platform that moves data between apps, for example Celigo, or Make for light flows.

    Fits: Several systems, or upkeep by a non-developer team.

    Limits: A monthly platform fee, and platform-specific logic.

  • C. Custom integration

    WooCommerce REST API and webhooks connected to the other system's API, with a queue, retries and logs, built as custom development.

    Fits: B2B prices, personalised files, multi-supplier routing or an unusual system.

    Limits: We build and maintain it, so it is quoted per project.

Often a mix: a connector or platform for the standard flows, plus custom logic for B2B prices, personalised files or multi-supplier routing. Built as custom development.

The Cmsmart angle

What is core, and what is built for you

Cmsmart Ecommerce is built on WooCommerce. The designer side is part of the product. The bridge to your other systems is custom development.

Core Core in Cmsmart Ecommerce

  • Each personalised order line carries its own design
  • The designer exports a print-ready PDF for a design
  • WooCommerce REST API and webhooks (WooCommerce core)

Custom Custom development

  • The bridge that sends a file or an order to another system
  • Field mapping, price-list logic and routing rules
  • Queue, retries, logs and alerts

Scope

Included, not included, and extra

Included

  • A data map of orders, files, variants, status and tracking
  • The bridge that sends the order and each line's print-ready file to the supplier API
  • Variant and print-area mapping for your products
  • Routing rules if you use more than one supplier
  • Status and tracking back to WooCommerce and the customer email
  • Queue, retries, logs and failed-order alerts
  • Testing on staging with your real order scenarios

Not included

  • The supplier's catalogue, pricing or production quality
  • Supplier fees and shipping costs
  • Implementing or licensing the other system itself (ERP, CRM, MIS or supplier account)
  • Fees charged by the other system, a connector or an integration platform
  • Changes inside the other system's configuration beyond the agreed scope

Extra, quoted separately

  • Printcart, a Netbase platform, as a print-side connection through its API. Endpoint details are agreed with its team in the assessment.
  • Shipping labels and carrier or 3PL links, see the shipping and 3PL service
  • Artwork approval before an order is released to production

What we need from you

  • Your supplier account, or a sandbox, with API access
  • The list of products and variants you sell, with print areas
  • Your rule for choosing a supplier, if there is more than one
  • Admin or sandbox access to the other system, and an API user with only the rights needed
  • A named owner on your side for each synced object (products, stock, prices, customers, orders)
  • A staging copy of your store, or approval to create one
  • Examples of real orders, including the awkward ones (partial shipments, refunds, custom items)
  • Your volumes: orders per day, number of products and the busiest days

Process

How an integration project runs

Each phase is a milestone, approved and invoiced one at a time in your dashboard. The timeline is set in the assessment, because it depends on your systems and volumes.

  1. Free integration assessment. We review your systems, the owner of each field, your volumes and API access, and tell you what is feasible.
  2. Architecture and data map (milestone 1). A signed-off design that states what syncs, which way, how often and which system owns each field.
  3. Build in sprints on staging, using sandbox accounts of your systems.
  4. User acceptance testing with your own order, price and file scenarios.
  5. Go-live with a cut-over plan, a back-fill of open orders and monitoring switched on.
  6. Support. Tickets in your dashboard, health checks, and updates when either system changes its API.

Enterprise support tier

For integrations your operations depend on

Response targets, monitoring and review cadence are set in your agreement, not on this page.

  • Monitoring of sync health and failed jobs, with a monthly sync report
  • A named team that stays after launch
  • A security review before go-live
  • WooCommerce and connected-system upgrades tested on staging first

Ask about enterprise support

Free assessment

See what connecting POD and fulfilment would take

Tell us about your store and the system. We reply with what is feasible, which route we would pick and a quote, with no obligation.

Book a free integration assessment How we run projects

FAQ

Frequently asked questions

Can the shopper's personalised design go to my POD supplier automatically?

Yes, as custom development. The Cmsmart designer keeps a design per order line and can export a print-ready file. The bridge sends that file by URL to the supplier API with the order, print area and variant.

Why not just use the supplier's own WooCommerce plugin?

A supplier plugin is a good choice when you sell the supplier's own catalogue products. It may not pass a shopper's own personalised file for each order line, so check its current documentation. That gap is what the bridge covers.

Can orders go to more than one supplier?

Yes. The integration layer can route by product, region or cost, for example one supplier for apparel and another for wall art or for a different country.

Which fulfilment providers can you connect?

Printful, Printify, Gelato, Gooten, Prodigi, CustomCat, SPOD, T-Pop, Teelaunch, Apliiq, Lulu Direct, Peecho, Printed Mint, Scalable Press, or your own print partner by API, SFTP or an email order sheet. Each section on this page says what we could verify.

What happens when the supplier rejects an order or is down?

The order waits in a queue and is retried. A rejection or repeated failure raises an alert, and the order shows its state in the admin so staff can act.

Does tracking come back to the store?

Yes. Tracking number and link return to the order in WooCommerce and to the customer email, by webhook or polling, depending on what the supplier offers.

How is the project priced?

There is no public price. After the free assessment you receive a quote, with the data map as milestone 1. Supplier fees are paid to the supplier.

Can you work with a client in my country?

Yes. Every Cmsmart service, from custom development, migration and integration to full store builds, is delivered remotely. Clients in any country and any industry can work with the team; Netbase has worked with clients in 80+ countries. Projects run online, through a written proposal, email or WhatsApp, and tickets in the Cmsmart dashboard.

Do you work in my industry?

Yes. Clients in any country and any industry can work with the team; Netbase has worked with clients in 80+ countries. Published Cmsmart projects include stores for web-to-print, merchandise and apparel, signage, packaging and labels, and gifts and promotional products. See the client work at cmsmart.net/projects.

How do I pay securely?

Contracts and payments go to the company, Netbase JSC: plans are paid through PayPal; services are invoiced by Netbase JSC under a written proposal and paid by bank transfer to Netbase JSC's company account or by PayPal Business. Cmsmart (Cmsmart Ecommerce) is the ecommerce brand of Netbase JSC, a company based in Hanoi, Vietnam.

Who do I talk to?

Talk to the CEO, Huy Nguyen (David): message him on WhatsApp at +84 937 869 689 or email project@cmsmart.net. The contact page at cmsmart.net/contact lists every channel, and Request a quote (cmsmart.net/project-proposal) sends your project brief to the team. Tell us the scope and we reply with a plan and a quote.

Learn more

Related tutorials from the community

All community guides

Who you work with

The team behind Cmsmart and its published work

  • 2012Netbase since 2012Cmsmart Ecommerce is a Netbase JSC company
  • 6,300+client projectssince 2012
  • 80+countriesclients worldwide
  • 17,157proposals writtenin our project system, live count

Client projects and countries: Netbase portfolio library and WorkSuite project records, as of Sep 2026. Proposals: records in our Cloodo WorkSuite project system, all-time, refreshed every 6 hours.

Huy Nguyen (David), Founder and CEO of Cmsmart

Talk to an ecommerce expert

Huy Nguyen (David)

Founder & CEO, Cmsmart · Netbase JSC

Every request is read by the team before you get a written scope and estimate.

Request a proposalChat with David on WhatsApp

Published Cmsmart projects

Project records from our portfolio. They show the wider work of the team, not this exact service.

Stores on Cmsmart Ecommerce

  • Customer logo: inkfront.com
  • Customer logo: weinkthat.com
  • Customer logo: botaksign.com
  • Customer logo: signalo.nl
  • Customer logo: ustickerit.com.au
  • Customer logo: clickprint.lk
  • Customer logo: storyblockplus.com
  • Customer logo: privatwelt24.de
POD and fulfilmentFree assessment
Have an ecommerce project in mind?

Tell us what you need — get a free consultation and a tailored quote.

Get a free quote
Ecommerce Solution
Client Portal
Meet Cmsmart

Cmsmart Ecommerce provides custom ecommerce and WooCommerce development services for web-to-print, product personalization, plugin support and API integration.

Cmsmart Ecommerce expert team

Web-to-print, WooCommerce, B2B and AI specialists who plan, build and support stores together.

Meet the team →
  • Cmsmart is a brand of Netbase JSC. We work remotely with clients in 80+ countries; contracts and payments go to Netbase JSC.
  • 91 Nguyen Chi Thanh Str, Dong Da Dist, Hanoi, Vietnam
  • Email: project@cmsmart.net
  • WhatsApp: +84 937 869 689
  • Contact page

Cmsmart Ecommerce — a Netbase JSC company. Copyright © 2012-2026 Cmsmart.net. All rights reserved.

Payment Method

Top