Knowledge BaseOMSMarketplace Integrations

Marketplace Integrations

Marketplace Integrations connect external platforms to ShipGenius. This article explains how integrations work, what each setting controls, and how to configure them correctly.

A Marketplace Integration connects an external platform to ShipGenius so that orders, inventory, and shipment data can flow between the two systems automatically. Currently supported integration partners are Shopify and Infoplus. Each integration has its own configuration specific to that platform, but the core structure covers sync settings, blueprint priority, shipment mappings, scheduled tasks, and SKU filters.

Integration Tabs Overview

Each integration in ShipGenius has six tabs: Overview, Settings, Shipment Mappings, Schedule, Errors, and Runs. Together these give you full visibility and control over how the integration operates.

  • Overview: summary of integration status, sync toggles, and recent activity
  • Settings: all configuration for the integration including API credentials, order settings, inventory settings, and platform-specific options
  • Shipment Mappings: maps external shipping service names from the platform to ShipGenius carrier services or Rate Groups
  • Schedule: configures how frequently each sync task runs
  • Errors: shows orders or records that failed to import and why
  • Runs: history of each sync task execution with timing and result information

Sync Settings

Each integration has three independent sync toggles that control what data flows between ShipGenius and the external platform:

  • Sync Orders: when active, new orders from the external platform are imported into ShipGenius on the configured schedule. When inactive, no orders are pulled in regardless of schedule settings.
  • Sync Shipments: when active, shipment confirmations and tracking numbers are exported back to the external platform after fulfillment. When inactive, the platform is never notified that orders shipped.
  • Sync Inventory: when active, inventory levels in ShipGenius are pushed to the external platform on the configured schedule. When inactive, inventory on the platform is never updated from ShipGenius.

The master Active toggle at the integration level overrides all three. If the integration is inactive, nothing syncs regardless of the individual toggle states.

Schedule

The Schedule tab controls how frequently each sync task runs. There are three independently scheduled tasks:

  • Order Import: how often ShipGenius pulls new orders from the external platform
  • Shipment Export: how often ShipGenius pushes shipment confirmations back to the external platform
  • Inventory Sync: how often ShipGenius pushes inventory levels to the external platform

Each task has a Measure (a number) and a Unit (MINUTE or HOUR) that together define the interval. A Measure of 15 and a Unit of MINUTE means the task runs every 15 minutes. Tasks can be individually toggled active or inactive from the Schedule tab without affecting the other tasks.

Task timing is managed by the ShipGenius task server. The next scheduled run time for each task is visible in the Runs tab.

Shipment Mappings

When an order arrives from an external platform, it includes a shipping service identifier from that platform, for example 'Standard Shipping' or a carrier service code. Shipment Mappings tell ShipGenius how to translate those external service identifiers into actual carrier services or Rate Groups.

Each mapping connects an external service identifier to either a specific carrier service and carrier account, or a Rate Group. It points to one or the other, not both simultaneously.

If an order arrives with a service identifier that has no mapping configured, the import will error. This is intentional. An unmapped service means the system has no way to determine how to fulfill that order correctly, and silently processing it with an assumption would cause fulfillment errors. All service identifiers coming from your external platform must have a mapping configured before orders using that service will import successfully.

Infoplus integrations have additional shipment mapping complexity due to parcel account configuration and external shipment post-back requirements. See the Infoplus Integration article for specifics.

Blueprint Priority

Each integration has its own blueprint priority list that determines which blueprint is applied to incoming orders. This is the marketplace-specific priority layer, evaluated before global priorities and before the default blueprint. See the Blueprint System article for a full explanation of how priority evaluation works.

The default blueprint is set per integration and acts as the final fallback if no priority entry matches an incoming order. It is strongly recommended to set this to an ERROR type blueprint so unmatched orders surface for review rather than processing silently with the wrong configuration.

SKU Filters

SKU filters let you control which orders get imported based on the SKUs they contain. There are two filter modes:

  • Whitelist: only import orders that contain at least one SKU from the filter list. Orders with none of the listed SKUs are ignored.
  • Blacklist: import all orders except those containing SKUs from the filter list. Orders with any listed SKU are ignored.

SKU filters are optional. If no filter list is configured, all orders are imported regardless of SKU content.

SKU Not Found Behavior

When an order arrives containing a SKU that does not exist in ShipGenius, there are three ways the system can handle it. This is configured per integration:

  • ERROR: the order import fails and the order is logged in the Errors tab. No partial import occurs. The order must be resolved manually before it will import.
  • IMPORT: the missing item is automatically created in ShipGenius using the information from the incoming order. The order imports successfully with the new item.
  • SKIP: the line containing the unknown SKU is dropped. The order imports with only the lines whose SKUs are known in ShipGenius. Use this carefully. It means orders may import missing items without any error surfacing.

Duplicate Order Handling

The Update Orders on Duplicate Import setting controls what happens when an order arrives from the platform with the same external order ID as one that already exists in ShipGenius. When enabled, ShipGenius will update the existing order with the new data, provided the order is in a state that allows updates. When disabled, duplicate imports are ignored and the existing order is left unchanged.

Sellers

Each integration can have multiple Sellers, which represent sub-sources within the external platform. What a Seller maps to depends on the integration partner. In Infoplus, a Seller corresponds to a Line of Business (LOB) and a Seller Source maps to the order source within that LOB. In Shopify, a Seller corresponds to a sales channel such as Online Store, POS, TikTok Shop, or any other connected channel.

Sellers allow you to filter and route orders differently based on where within the external platform they originated. Blueprint priority can be configured at the Seller level to override the integration-level priority for orders from that specific source.

Errors and Runs

The Errors tab shows any orders or records that failed to import along with the reason for the failure. Common causes include unmapped shipping services, unknown SKUs (when SKU Not Found is set to ERROR), or API credential issues. Errors should be reviewed regularly to ensure orders are not stuck.

The Runs tab shows the history of every task execution including when it started, how long it ran, and what the result was. Use this to verify tasks are running on schedule and to diagnose timing issues.

FAQs

What happens if I turn off the master Active toggle?

All sync stops immediately. No orders import, no shipments export, no inventory syncs, regardless of the individual sync toggle states or schedule configuration.

What happens if an order arrives with a shipping service that has no mapping?

The import errors. Every shipping service identifier coming from your external platform must have a mapping configured. Check the Errors tab to see which service identifier caused the failure, then add the mapping in the Shipment Mappings tab.

What is the difference between a shipment mapping pointing to a carrier service vs. a Rate Group?

A carrier service mapping locks the order to a specific service on a specific account with no rate comparison. A Rate Group mapping tells ShipGenius to evaluate multiple services at fulfillment time and select the best one based on your priority and filter configuration. Use Rate Groups when you want the system to optimize automatically. Use direct carrier service mappings when the service for that order type is always fixed.

What does SKIP for SKU Not Found actually do to the order?

It drops only the lines with unknown SKUs and imports the rest of the order. The order comes in without those lines and without any error surfacing. Use this setting carefully. It can result in orders being fulfilled with missing items if SKUs are not kept in sync between ShipGenius and your external platform.

Where do I configure Shopify-specific or Infoplus-specific settings?

In the Settings tab of the integration. Each integration partner has its own settings section in addition to the standard settings shared across all integrations. See the platform-specific integration articles for details.