Skip to content

FousTraverse Portal

Get your Traverse Portal charges through an API

Read compliance charges, Charge Detail, disputes and reversals from a retailer's Traverse Portal with one API call each. Or have a workflow check Find Charges every Monday and email you the new OTIF, Small Parcel and ASN charges.

Works with your own Traverse Portal account. Fous is an independent product.

What you can build on the Traverse Portal

  • Find compliance charges

    Build this

    Searches Find Charges under Vendor Tools and reads the charges listed, for the charge numbers you give or for everything the list shows.

    Takes
    Charge numbers (optional)
    Returns
    Charge number, program, charge type, description, PO number, charge amount, deduction date
  • Read a charge's detail

    Build this

    Opens the Charge Detail page for one charge number and reads everything it shows, with the reports listed under Related Information.

    Takes
    Charge number
    Returns
    Charge number, charge type, rule, description, PO number, amount, dates, available reports
  • Check disputes and reversals

    Build this

    Reads Find Disputes, Find Resolved Disputes and Find Reversals under Vendor Tools, so you see where each dispute stands and which charges were reversed.

    Takes
    Charge numbers (optional)
    Returns
    Charge number, dispute status, submitted date, resolution, reversal amount
  • Create a dispute for a charge

    Build this

    Opens Create Disputes under Vendor Tools, enters the charge number, adds your comments and proof as attachments, and submits the dispute.

    Takes
    Charge number, comments, proof document
    Returns
    Charge number, submitted, dispute reference

Automate the Traverse Portal with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • New compliance charges, grouped by program

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    Read every charge listed in Find Charges.
    Step 2
    Keep the charges that were not there on the last run.
    Step 3
    Email you the list grouped by OTIF, Small Parcel and ASN, with PO number and amount.
  • Charges close to the 45-day dispute window

    Build this
    Starts
    Every weekday at 7:30
    Step 1
    Read every charge listed in Find Charges.
    Step 2
    Read Find Disputes and drop the charges already disputed.
    Step 3
    Keep the charges deducted 35 to 45 days ago and email you the list.
  • Dispute outcomes posted to your deductions system

    Build this
    Starts
    Every day at 17:00
    Step 1
    Read the records in Find Resolved Disputes and Find Reversals.
    Step 2
    Keep the ones that changed since the last run, and stop when there are none.
    Step 3
    Post each one to your ERP or deductions system's webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Find compliance charges” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "cvs.traversesystems.com/find_compliance_charges",
    "input": {
      "charge_numbers": []
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "charges": [
      {
        "charge_number": "50817342-OT",
        "program": "OTIF",
        "charge_type": "Compliance",
        "description": "Shipment arrived after the must-arrive-by date",
        "po_number": "7104558",
        "amount": 412.6,
        "deduction_date": "2026-11-02"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

The Traverse Portal’s own options

Traverse documents two APIs, the Platform API and the Vision Data API, which it provides to its customers. The Platform API's Charge API is described for Performance Center customers, and the documentation does not describe API access for vendors. As a vendor you use the Traverse Portal, where charges, disputes and reversals sit under Vendor Tools.

OptionWhat it coversWhat it takes
Platform APICharge API: transmitted or approved charges by fiscal year and month. Trouble API: lists, details and new Trouble records for a PO.An API key sent as KeyName:ApiKey with Basic Authentication. The Charge API is described for Performance Center customers.
Vision Data APIOne of the two APIs Traverse provides to its customers to send or extract data.Provided by Traverse to its customers.
The Traverse Portal by handFind Charges, Charge Detail with a Chargeback Detail PDF, Create Disputes, Find Disputes, Find Resolved Disputes and Find Reversals.Your vendor account on the retailer's Traverse Portal, such as cvs.traversesystems.com.

Read on November 12, 2026: Traverse Systems API documentation, Traverse Platform API, CVS compliance fines in the Traverse Portal.

Signing in to the Traverse Portal

CVS's Traverse Portal is at cvs.traversesystems.com, and you sign in there with your vendor account. With Fous you sign in once through the portal's own sign-in with your own account: the login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

The address names the retailer
CVS's Traverse Portal is at cvs.traversesystems.com. A method is built on the portal you sign in to, so you build one for each retailer's portal you use.
45 days to dispute at CVS
CVS compliance fines can no longer be disputed 45 days after the charge deduction date, and after 365 days they can no longer be found in the Traverse Portal.
The charge number tells the program
At CVS, charge numbers end in -OT for OTIF, -SP for Small Parcel and -AS for ASN. A weekly compliance summary email lists the charge numbers to search.
Attachments and Comments are yours to add
In Create Disputes, most fields fill in from the charge number. Attachments and Comments need your input, and the proof needed depends on the metric the charge is for.

More in Retail: vendor portals (North America)

Other industries: Morrisons Supplier Portal, Verizon Enterprise Center, Thumbtack Pro, Workday supplier portal, Sage Intacct, 微信公众平台.

Frequently asked questions

Not one documented for vendors. Traverse provides the Platform API and the Vision Data API to its customers, and its Charge API is described for Performance Center customers. As a vendor you have the Traverse Portal, with charges, disputes and reversals under Vendor Tools.

45 days from the charge deduction date. After that the fine is no longer eligible for dispute, and after 365 days it can no longer be searched in the Traverse Portal. A workflow can check Find Charges each weekday and email you the charges close to that limit.

They name the CVS program the charge comes from: -OT is OTIF (On-Time In-Full), -SP is Small Parcel and -AS is ASN (Advanced Ship Notice).

Under Vendor Tools: Find Disputes lists the disputes you submitted, Find Resolved Disputes the ones that were decided and Find Reversals the charges that were reversed. A method can read all three and return them as JSON.

No. Fous is an independent product. You use it with your own Traverse Portal account, and a method reads and does only what that account can.

Put Traverse Portal behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextmyUNFIRithum OrderStreamSyndigo CXHMorrisons Supplier PortalHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Traverse Portal (Traverse Systems (SPS Commerce)). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.