Connect Geneva10 WMS (G10) to Pipe17

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

  • An active client account with G10 Fulfillment (Geneva10).
  • Access to Integrations in the app.
  • The connection details G10 gives you: the Fulfillment Orders Api URL, the Purchase Orders Api URL (only if you push arrivals), the security token, and your G10 AccountID (for example, ABCTEST).
  • The list of warehouses G10 assigned to your account, as warehouse ID and name pairs.
  • The ship method values G10 accepts for your account. Each shipping request sends its shipping code to G10 as the ship method, so your orders need shipping codes that match these values.

Get your credentials from G10

G10 has no self-service portal for API credentials. Your G10 account team sets up the integration and sends you the values.

  1. Contact your G10 account manager, or reach G10 through the G10 Fulfillment contact page, and ask to set up an API integration with Pipe17.
  2. Ask G10 for:
    • The URL that receives outbound orders (Outbound-Order). You enter it as the Fulfillment Orders Api URL.
    • The URL that receives purchase orders (Purchase-Order). You enter it as the Purchase Orders Api URL.
    • The security token that G10 expects in the x-csrf-token header. The app sends one token to both URLs, so ask G10 to confirm that the same token works for both.
    • Your WMS AccountID.
    • Your warehouse IDs and names, and the ship method values for your account.
  3. G10 sends ship confirmations, receipt confirmations and the inventory feed to a webhook. Contact Pipe17 support for the webhook URL to give G10, and ask G10 to send all three to it. Every webhook must carry your AccountID, because the app uses it to find your integration.
  4. If G10 gives you test values first (such as a test AccountID), replace them with the production values before you go live.
  5. Store the security token like a password. Don't share it by email or chat.

Connect in the app

  1. Navigate to Integrations in the app.
  2. Click Add Integration, and then select Geneva10 WMS. The connect pop-up opens.
Connect g10 pop-up
  1. In Fulfillment Orders Api URL, enter the outbound order URL from G10. It's required when Push shipping requests to G10 is on.
  2. In Purchase Orders Api URL, enter the purchase order URL from G10. It's required when Push arrivals (Purchase Orders) to G10 is on.
  3. In G10 Security Token (x-csrf-token), enter the security token.
  4. In G10 AccountID, enter your AccountID exactly as G10 gave it.
  5. Click Connect.

Note: The app doesn't call G10 when you connect. It checks only that the token and AccountID are filled in. A wrong URL or token shows up later, when the first shipping request or arrival fails.

Note: To add the integration without credentials, click Add without credentials. The integration is added, but it doesn't sync until you enter the credentials on the Connection Details tab and save.

Confirm the connection

  1. On Integrations, check that the integration shows Connected. If it shows Error or Not Configured, open the Connection Details tab, fill in any missing value named in the error (for example, Fulfillment Orders Api URL when Push shipping requests to G10 is on), and save.
  2. Make sure the integration switch is on.
  3. In the integration settings, under Locations, enter each G10 warehouse in Warehouse list (WarehouseID:DisplayName), for example 1:Main DC. The warehouse ID must match G10's exactly. Leave Pull locations from G10 (settings-managed) on (it's on by default). Within about 5 minutes, the warehouses appear as locations in the app.
  4. Route a test order to one of your G10 locations, and make sure its shipping code matches a G10 ship method. Enter its order ID in Process only shipping requests with specific order IDs, and then turn on Push shipping requests to G10.
  5. Wait about 5 minutes, and then open the order in the app. Its shipping request should show Sent to Fulfillment. If it shows Failed, check the location, the shipping code, and the URL and token. Ask G10 to confirm that they received the order.
  6. Turn on the inbound flows you use: Pull fulfillment information from G10, Pull inventory information from G10 and Pull receipts from G10. These flows run only when G10 sends a webhook, so fulfillments appear after G10 ships the order. To test inventory with a few SKUs first, enter them in Process inventory only for these SKU patterns.
  7. If you send inbound inventory to G10, turn on Push arrivals (Purchase Orders) to G10. To test with one arrival first, enter its order ID in Process only arrivals for specific order IDs. The arrival's destination must be one of your G10 locations.
  8. Clear the test filters so the app processes all records.

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. A plain value matches a SKU exactly (not case-sensitive); a value wrapped in slashes, such as /^ABC/, is a regular expression. 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 Pushed every 5 minutes to the Fulfillment Orders Api 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 every 5 minutes to the Purchase Orders Api URL so the warehouse can receive inbound inventory. Only arrivals going to one of your G10 locations are sent.
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 G10 → Pipe17 (from settings) G10 has no location API. When Pull locations from G10 (settings-managed) is on, the app creates a location for each entry in Warehouse list (WarehouseID:DisplayName) every 5 minutes.

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

  • The integration shows Error after you connect or turn on a flow.
    The error names the missing value, such as Missing required setting: Fulfillment Orders Api URL. The URL is required only for the push flow you turned on. Enter the value on the Connection Details tab and save.
  • A shipping request or arrival shows Failed right after it is pushed.
    The app marks it Failed when its location isn't one of the warehouses in Warehouse list (WarehouseID:DisplayName), when a required field such as the ship method is missing, or when G10 rejects the request (often a wrong URL or token). Fix the cause before you push the record again.
  • Shipping requests or arrivals are not reaching G10.
    Confirm the Fulfillment Orders Api URL and Purchase Orders Api URL 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.
  • Shipping requests fail because of the ship method.
    G10 has no ship methods API, and the integration has no ship method setting. The app sends the shipping request's shipping code to G10 as the ship method. If the shipping code is missing, the app marks the shipping request Failed. Make sure your orders carry shipping codes that match the ship method values G10 gave you.
  • 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 platform page.
  • Submit a support request with as much relevant detail as possible. Learn how to submit a request.

We’re here to help you succeed with your operations.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.