# Sync product data with Product Catalogue
URL: https://support.starshipit.com/articles/14700000001007-sync-product-data-with-product-catalogue
Canonical: https://support.starshipit.com/articles/14700000001007-sync-product-data-with-product-catalogue
Markdown: https://support.starshipit.com/articles/14700000001007-sync-product-data-with-product-catalogue.md
Updated: 2026-06-18

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Sync SKU, dimensions, weight, customs, and fulfilment data into Starshipit's Product Catalogue through the Starshipit API.

Sync product data with Starshipit's Product Catalogue when another system owns product master data and Starshipit needs that data for fulfilment, customs, packing, or live rates.

## What to sync

Product Catalogue data commonly includes:

- SKU.
- Product name or description.
- Weight and dimensions.
- HS or tariff code.
- Country of origin.
- Customs description.
- Cost price or declared value fields.
- Bin location or fulfilment location.

## Choose your source of truth

Decide whether Starshipit should replace missing order data with Product Catalogue values or whether incoming order data should remain the source of truth.

| Field type | Common source | Notes |
| --- | --- | --- |
| SKU | ERP, ecommerce platform, PIM, or WMS | SKUs must match consistently for catalogue data to apply. |
| Weight and dimensions | Product Catalogue, ERP, PIM, or ecommerce platform | Accurate dimensions improve rates and packaging decisions. |
| Customs data | Product Catalogue, ERP, or PIM | Missing customs data can block international labels. |
| Bin location | WMS, ERP, or Product Catalogue | Useful for picking and packing workflows. |

## Recommended workflow

1. Export or retrieve product data from the source system.
2. Normalise SKUs before sending data to Starshipit.
3. Sync a small product set first.
4. Confirm the Product Catalogue shows the expected values.
5. Create or import a test order with matching SKUs.
6. Confirm Starshipit applies the catalogue data in the order, checkout, or fulfilment workflow you are testing.
7. Expand the sync once the mapping is correct.

## Endpoint map

[Open the Starshipit API reference](/developers/api-reference/starshipit#products) for request fields and response models.

| Step | Endpoint | Use it to |
| --- | --- | --- |
| List products | `GET /api/products` | Reconcile Product Catalogue data with your source system. |
| Add product data | `POST /api/products` | Create new Product Catalogue records. |
| Update product data | `PUT /api/products/update` | Keep SKU, weight, dimensions, customs, and fulfilment fields current. |
| Delete product data | `DELETE /api/products/delete` | Remove records only when your source system confirms they should no longer sync. |
| Download CSV template | `GET /api/products/template` | Get the current Product Catalogue import template. |
| Import product CSV | `POST /api/products/import` | Import Product Catalogue records from a CSV file. |
| Export product CSV | `GET /api/products/export` | Export Product Catalogue records for reconciliation or backup. |

## Keep product sync reliable

- Use stable SKUs and avoid whitespace or casing differences.
- Send complete product records where your source system can provide them.
- Log product IDs, SKUs, request status, and response errors.
- Treat repeated validation errors as data-quality issues, not retry-only issues.
- Reconcile a sample of synced products after each major mapping change.

## Related Starshipit guides

- [Product Catalogue](/articles/integrations/product-catalogue/product-catalogue)
- [Add and manage products in the Product Catalogue](/articles/integrations/product-catalogue/add-and-manage-products-in-the-product-catalogue)
- [Configure Product Catalogue settings](/articles/integrations/product-catalogue/configure-product-catalogue-settings)
- [Starshipit API reference](/developers/api-reference/starshipit#products)