Bulk Operations

What this means in plain English

These endpoints mirror the legacy G-Commerce bulk APIs (products_bulk, products_feed, products_export) using JSON over REST. They replace the former REST CSV upload flow documented under Bulk Import.

Migrating from G-Commerce

Legacy endpoint	Glass Next endpoint
`POST /api/products_bulk`	`POST /vendor/products/bulk-update`
`POST /api/products_feed`	`POST /vendor/products/bulk-upload`
`GET /api/products_export`	`GET /vendor/products/export`

Field name mapping

Legacy field	Glass Next field	Notes
`product_id`	`product_id`	UUID in Glass Next (was numeric in legacy)
`code`	`code`	Maps to product/variant SKU
`product`	`items[].product`	Product name on upload
`full_description`	`items[].full_description`	Maps to product description
`vendor_price`	`vendor_price`	Variant vendor (cost) price. The customer retail price is derived server-side as `vendor_price × (1 + commission %)` — it cannot be set directly.
`amount`	`amount`	Inventory stock (absolute)
`manufacturer_name`	`manufacturer_name`	Product manufacturer
`manufacturer_part_number`	`manufacturer_part_number`	Variant part number
`unspsc`	`unspsc`	Stored as variant `unspc`
`commodity_code`	`commodity_code`	Product `commodityCode` (max 28)
`category_ids`	`category_ids`	Existing category UUID(s) only — use List Categories

Metadata-only fields (upload)

These fields are accepted on bulk upload and stored as product metadata (metaobjects), not as first-class columns:

min_qty, weight, free_shipping, abilityone, made_in_usa, green_product

Endpoints

Operation	Method	Path
Bulk Update	POST	`/vendor/products/bulk-update`
Bulk Upload	POST	`/vendor/products/bulk-upload`
Bulk Export	GET	`/vendor/products/export`

Authentication

Use Authorization: Bearer {token} from Login — not legacy Basic auth (EMAIL:API_KEY).