:books: Learn about the important terminologies related to our API here!

Cymbio

Cymbio is a dropship/marketplace automation platform that streamlines data between suppliers and retailers to enable online and in-store sales. Cymbio can synchronize, manage, normalize and serve products data including imagery, inventory, orders, and billing data.

Supplier/Brand

A supplier is a Cymbio’s client and an entity that holds products and inventory in a warehouse (or warehouses) and can receive fulfillment, fulfill them, partially fulfill or cancel them.

Retailer

A retailer is a business entity that has a commercial agreement with a supplier to buy and/or to resell the supplier’s goods.

Model Vs. Variant

A model is an aggregation of variants, sometimes referred to as a style or a parent product. Variants are unique products that are differentiated by options. For example, you can have a T-shirt that is manufactured in many colors and sizes. The size and color are the options and each variant has a unique combination of the two. Simple models or simple products have only 1 variant and therefore might have no options at all. In Cymbio’s DB each variant is linked to one supplier and has an SKU which is a mandatory field for a variant.

Warehouse

A warehouse is a generic name for a source of inventory and can be a real warehouse, a distribution center, a physical store, or even a virtual inventory source like an eCom website. Cymbio supports multi-warehouses, thus, each brand can have multiple warehouses/inventory sources. Some warehouses have multiple inventory buckets (or pots in the EU) as suppliers tend to split and allocate inventory for various business units and operations. In most integrations, Cymbio supports the aggregation of multiple buckets into 1 or multiple warehouses in Cymbio’s DB.

Inventory

Each variant has a unique quantity for each warehouse it is stored in. We expect to receive ATS (Available to sell) or FTS (Free to sell) inventory and not on-hand.

Order

An order in Cymbio DB is an object that was received from a retailer or pulled from the retailer’s platform/website and represents how the order was pushed or captured prior to being split to various warehouses or brands or manipulated for the use of the brand based on the brands' specifications. An order will be linked to 1 or many fulfillments based on the sources and availability of the items. As a retailer utilizing the API, you’ll be expected to place orders and get order statuses.

Fulfillment

A fulfillment is either a part of a full order that needs to be fulfilled by a brand’s warehouse. The fulfillment holds all the necessary data needed for the brand in order to fulfill the retailer’s order. As a brand working with Cymbio and utilizing the API, you’ll be expected to grab fulfillments and update fulfillments’ statuses.

The following diagram explains the basic flow in our ecosystem:

734734

:email: Need help?

If you've run into an issue, please report it by emailing [email protected]. Include a description of the issue you're experiencing, provide steps to recreate it, and share the API call you did including the body/payload and the full responses that you received. A member of our team will reach out for additional info if needed.