The G10 connector integrates Pipe17 with the G10 (WMS Geneva) warehouse management system. Pipe17 pushes shipping requests and arrivals to G10 for fulfillment, and G10 sends fulfillment, receipt, and inventory updates back to Pipe17 through webhooks. This keeps your orders, inbound shipments, and stock levels aligned across both systems without manual data entry.
The connector lets you:
- Push shipping requests (fulfillment orders) for both sales orders and transfer orders to G10.
- Push arrivals to G10 so the warehouse can receive inbound inventory.
- Receive fulfillment updates from G10, including lot number and expiry date for transfer orders.
- Receive receipt and inventory updates from G10 by webhook.
- Map your G10 warehouses to Pipe17 locations.
Setup
Before you begin, have the following ready:
- A G10 (Geneva10) account.
- The G10-provided Fulfillment Orders Api URL (where Pipe17 posts outbound orders).
- The G10-provided Purchase Orders Api URL (where Pipe17 posts purchase orders/arrivals).
- Your G10 Security Token (x-csrf-token).
- Your G10 AccountID (for example,
ABCTEST). - The list of warehouses G10 assigned to your account, in
locationId:locationNameformat. - The list of fulfillment methods G10 supports for your account.
To connect G10 to Pipe17:
- Navigate to Integrations in the app and select Add integration.
- Select Geneva10 WMS from the connector list.
- Enter the Fulfillment Orders Api URL. This is required when Push shipping requests to G10 is enabled.
- Enter the Purchase Orders Api URL. This is required when Push arrivals (Purchase Orders) to G10 is enabled.
- Enter your G10 Security Token (x-csrf-token).
- Enter your G10 AccountID.
- Select Connect.
- After connecting, open the integration settings to configure locations, fulfillment methods, and flow options (see Settings).
To add the integration and enter credentials later, select Add without credentials.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Locations: Warehouse list (WarehouseID:DisplayName) | Maps your G10 warehouses to Pipe17 locations. G10 has no location API, so enter each warehouse manually as locationId:locationName, comma-separated. Each G10 client has a unique warehouse list. |
Manually configured; no default |
| Shipping request: Process only shipping requests with specific order IDs | Restricts which shipping requests Pipe17 pushes to G10. Used mainly to limit records during testing. | Optional; empty means no filter |
| Inventory: Process inventory only for these SKU patterns | Restricts which inventory records Pipe17 processes from G10. Used mainly during testing. | Optional; empty means no filter |
| Arrivals: Process only arrivals for specific order IDs | Restricts which arrivals Pipe17 pushes to G10. Used mainly during testing. | Optional; empty means no filter |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Shipping requests (fulfillment orders) | Pipe17 → G10 | Sent to the G10 webhook URL. Covers both sales orders and transfer orders; the request shape differs slightly between the two. Transfer fulfillments are sent per container. |
| Arrivals | Pipe17 → G10 | Pushed to G10 so the warehouse can receive inbound inventory. |
| Fulfillments | G10 → Pipe17 | Received by webhook. Lot number and expiry date are exposed at the mapping level, primarily for transfer orders. |
| Receipts | G10 → Pipe17 | Received by webhook. |
| Inventory | G10 → Pipe17 | Received by webhook. |
| Locations | Configured in Pipe17 | Not synced. G10 has no location API, so warehouses are entered manually in the Locations setting. |
Because G10 sends fulfillments, receipts, and inventory by webhook only, the connector cannot pull this data on a schedule. There are no integration actions to trigger these flows manually.
Troubleshooting
-
Shipping requests or arrivals are not reaching G10.
Confirm both webhook URLs are entered correctly and that the security token is valid for both endpoints. Also check that any active shipping request or arrivals filter is not excluding the records you expect. -
Webhook updates are applied to the wrong integration during testing.
G10 identifies the integration by account ID, and every webhook carries that account ID. If more than one active integration uses the same test account ID, updates can be routed to the wrong one. Keep only a single active integration per test account ID. -
Fulfillment methods are missing or rejected.
G10 has no fulfillment methods API, so the list is entered manually. Confirm the fulfillment methods in the integration settings match the list G10 provided for your account. -
Inventory or fulfillments are not appearing in Pipe17.
These flows are webhook-driven, so Pipe17 receives them only when G10 sends them. Confirm G10 is configured to send webhooks to your integration and that the account ID on the webhook matches this integration. -
Lot number or expiry date is missing on a fulfillment.
These fields are exposed at the mapping level and apply mainly to transfer orders. Confirm the mapping is configured and that G10 included the values in the webhook payload.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the app page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
- For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments