Oracle PeopleSoft and ShipStation integration

What moves between them

Purchase orders and requisitions flow from Oracle PeopleSoft into ShipStation as orders. ml-connector reads PeopleSoft requisition status and purchase order details, extracts vendor and item information, and creates corresponding ShipStation orders with the PeopleSoft requisition ID as the idempotency key. ShipStation sends webhook notifications when orders ship (SHIP_NOTIFY) or are rejected; ml-connector receives the webhook, extracts the shipment tracking and status, and writes it back to the PeopleSoft requisition or PO record via SOAP Component Interface calls. Frequency depends on your procurement cycle; for urgent shipments ml-connector can poll PeopleSoft every hour, and for regular supply ml-connector processes them once per day.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the PeopleSoft OPRID and password (or OAuth2 token for 8.58+) for REST endpoint access, and the ShipStation API Key for V2 endpoints. The connector reads PeopleSoft requisitions by date range filter to avoid full-table scans, extracts vendor, item, and quantity data, and creates ShipStation orders with natural keys (PeopleSoft requisition ID) to prevent duplicate orders if the flow retries. ShipStation webhook events arrive as pointers; ml-connector immediately fetches the full shipment record via authenticated GET, validates the signature, and writes the tracking number and status back to PeopleSoft. Since ShipStation datetime is PST/PDT but PeopleSoft uses the customer's local timezone, ml-connector converts all timestamps on ingest. PeopleSoft REST endpoints are read-only, so the connector uses SOAP Component Interfaces to update requisition status fields, which requires the admin to activate those services in Integration Broker. Rate limits are enforced on ShipStation (40 or 200 per minute depending on API version), so ml-connector tracks remaining quota and backs off if nearing the limit. Every record carries an audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company sources direct-ship components and subassemblies through multiple vendors. Their procurement team creates requisitions in Oracle PeopleSoft, selecting vendors and quantities for each item. Historically, a supply coordinator would print the requisitions, email them to the vendors, and track shipments in vendor emails and phone calls. With PeopleSoft and ShipStation connected, requisitions flow automatically into ShipStation as orders, vendor shipments route through ShipStation for consolidated tracking, and shipment notifications update the PeopleSoft record in real time. The procurement team now sees delivery status inside PeopleSoft without switching tools or waiting for manual email updates.

What you can do

• •Read purchase orders and requisitions from Oracle PeopleSoft and create corresponding orders in ShipStation with vendor and item details.
• •Receive ShipStation shipment notifications via webhook and update PeopleSoft requisition status, tracking number, and expected delivery date.
• •Authenticate to Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer token (PeopleTools 8.58+) and ShipStation with API Key.
• •Handle timezone conversion from ShipStation PST/PDT to customer's local timezone, and prevent duplicate orders by using PeopleSoft requisition ID as the natural key.
• •Track ShipStation rate limits and back off requests to avoid throttling, with automatic retry and full audit trail for every record synced between systems.

Questions

What data moves between Oracle PeopleSoft and ShipStation?

Purchase orders and requisitions move from PeopleSoft into ShipStation as orders. When a shipment completes in ShipStation, the tracking number, carrier, and delivery status flow back into PeopleSoft. Vendor master data and item master data from PeopleSoft populate the ShipStation order header and line items, so items map correctly across both systems.

How does ml-connector handle PeopleSoft's self-hosted architecture and unique hostname?

ml-connector stores the full PeopleSoft instance hostname, port, and node name per customer in encrypted configuration, since PeopleSoft has no shared API base URL. Authentication uses HTTP Basic Auth (OPRID/password) or OAuth2 tokens on PeopleTools 8.58+. The connector explicitly activates required SOAP Component Interface services in Integration Broker during setup so status updates can write back to requisitions.

Does the integration handle ShipStation's timezone and rate limits?

Yes. ShipStation datetimes are in PST/PDT, so ml-connector converts all shipment timestamps to the customer's local timezone on ingest. ShipStation enforces rate limits (40 or 200 requests per minute depending on API version), and ml-connector tracks remaining quota per call, backing off if nearing the limit to avoid throttling errors.