Sage Supply Chain Intelligence (formerly Anvyl) centralizes purchase orders, products, suppliers, and logistics milestones so ops teams can track orders from issue to delivery and spot issues early. Connecting Sage Supply Chain Intelligence to Parabola lets supply-chain, finance, and ops teams pull PO, shipment, and product data into the same flows they use for three-way matches, landed-cost analysis, supplier scorecards, and exception alerts, without writing code. To learn more about SSCI, connect with an expert.Documentation Index
Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Pull from Sage Supply Chain Intelligence
The Pull from Sage Supply Chain Intelligence step brings live PO, shipment, and product data from your SSCI account into Parabola so you can transform it, blend it with data from other systems, and trigger alerts on custom logic.How to authenticate
Get your credentials from Sage Supply Chain Intelligence
- Log in to Sage Supply Chain Intelligence and click your avatar, then click My Account.
- On the Your Account page, click GENERATE API KEY.
- The API key appears as a string of letters, numbers, and symbols. Copy and store it; the string will be hidden on subsequent visits.
Available data
The Pull from Sage Supply Chain Intelligence step gives you access to the following records:- Purchase orders and lines: PO number, supplier, status, ship-to and location, shipping method, target and expected ship and delivery dates, currency, created and updated timestamps, and line items (SKU/part, quantity ordered, quantity received, unit price, UOM, notes, tags).
- Shipments and tracking: Shipment identifiers (containers, bills of lading, airway bills), carrier and mode, ship-from and ship-to locations, estimated and actual pickup, departure, arrival, and delivery timestamps, milestone statuses (to be shipped, in transit, delivered, received, closed), and quantities by line or SKU.
- Products and parts: SKU/part number, name and description, category and tags, default UOM, supplier relationships, commercial identifiers (UPC, ASIN), HTS and tariff classification fields, pricing brackets (currency, unit price, minimum order quantity), and lead-time days by supplier or break point.
Common use cases
- Three-way match and discrepancy detection: Compare SSCI purchase orders against delivery receipts and supplier invoices, then post matched records to NetSuite or QuickBooks Online and route exceptions to Slack or email.
- Landed cost analysis: Combine SSCI purchase order data with freight from Flexport, duty files, and accessorials to calculate true landed cost per SKU and shipment.
- Live PO tracking and reporting: Blend SSCI POs with shipment milestones and ETAs to give ops a single dashboard, then export to Google Drive, Smartsheet, or Snowflake for cross-functional teams.
- Split shipment management: Match SSCI order data with delivery updates to track and create split shipments, keeping quantities and statuses accurate across systems.
- HTS classification: Extract product and supplier data from SSCI to classify SKUs by HTS code and standardize tariff data for customs, then sync the cleaned mapping back into NetSuite or your PLM.
- Supplier scorecards: Calculate supplier lead times, milestone completion, and on-time delivery rates, then deliver weekly scorecards to procurement via Slack, email, or Smartsheet.
- Exception alerting: Send a Slack or email alert when orders are delayed, shipments miss milestones, quantities don’t reconcile, or supplier timelines slip beyond plan.
- Order data enrichment: Use product data and attributes from systems like NetSuite or your PLM to fill in missing fields on SSCI orders and lines via a Send to an API step.
Tips for using Parabola with Sage Supply Chain Intelligence
- Normalize identifiers early. Map PO numbers, SKUs, and supplier IDs to your ERP and PLM keys at the top of the flow so joins downstream stay reliable.
- Blend shipments with POs. Computing real-time status, expected vs. actual dates, and exceptions usually requires both endpoints joined on PO number.
- Match cadence to use case. Hourly for active ETA monitoring, daily for three-way matches, weekly for supplier scorecards and lead-time reviews.
- Push only exceptions to chat. Calculate price, quantity, or date mismatches in Parabola and send only the meaningful exceptions to Slack or email so the channel stays usable.
- Keep landed cost accurate. Join SSCI line-item prices and quantities with freight, duty, and accessorial data to calculate landed cost per SKU, order, and shipment.
- Store lead-time rules in Parabola tables. Production and transit lead times change. Holding them in a Parabola table makes them easy to update without rebuilding the flow.
FAQ
Can I push data back into Sage Supply Chain Intelligence?
The Pull from Sage Supply Chain Intelligence step is read-only. To write back (for example, updating a PO or filling in line-item fields), use a generic Send to an API step pointed at the relevant SSCI endpoint with your API key.Where do I find my API key after I’ve left the page?
The key is shown only once. If you’ve lost it, log back in to My Account in SSCI and generate a new key, then update the credential in your Parabola Pull from Sage Supply Chain Intelligence step.Can I pull from multiple SSCI accounts in one flow?
Yes. Add multiple Pull from Sage Supply Chain Intelligence steps and authorize each with a different API key, then union the results downstream.With Sage Supply Chain Intelligence and Parabola connected, the three-way matches, supplier scorecards, and landed-cost reports your team rebuilds every week run on a schedule, with exceptions landing in the systems where procurement, finance, and ops already work.