What this connector can sync

Capabilities depend on the scopes and endpoints approved for your seller account. The plugin does not mark the account Connected until its Test Connection succeeds.

Required account and credentials

Connection type: Partner Approval

Use a seller/developer account owned by your business. Request only the scopes required for orders, products, inventory, fulfilment, returns or settlements.

OAuth callback URL:https://gstkhata.com/wp-json/agbp/v1/marketplace/oauth/callback/myntra

Webhook URL: Open Marketplace Connections, save the account, then copy its unique Webhook URL.

Step-by-step setup

1. Request PPMP/Omni partner integration approval.
2. Collect seller/facility identifiers and approved endpoints.
3. Enter the approval reference and issued access token.
4. Test the approved endpoint.
5. Map facilities to plugin warehouses before inventory sync.

SKU and warehouse mapping

Match priority is seller SKU → variant SKU → barcode/EAN/UPC → platform listing ID → product SKU. Unmapped items remain quarantined and never deduct stock automatically.

• Map each marketplace facility/store to a plugin warehouse or rack.
• Set safety stock buffer and stock deduction stage.
• Confirm service/digital items as non-shippable.
• Run the first sync and inspect Stock Reservations before dispatch.

Orders, labels, returns and settlements

Official label/AWB is used when supplied by the authorised marketplace API. The built-in packing label is a fallback and is not presented as a marketplace-approved carrier label.

• Order import creates an idempotent shipment record.
• Mapped physical items reserve stock.
• Cancellation releases reservation.
• Accepted sellable return may restore stock; damaged return remains quarantined.
• Fee and payout data is sent to existing reconciliation reports when the API exposes it.

Common errors

Official documentation

Open official documentation ↗