The promotional-products industry has made real progress on data connectivity.
PromoStandards has created common infrastructure. Major suppliers expose more structured product, pricing, and inventory information. Platforms are building deeper integrations. The direction is unquestionably positive.
And yet, an experienced operator still spends a surprising amount of the day inside supplier websites.
Why does portal work survive in an API world?
Because an API exposes what it exposes.
The complete workflow may require a proof, a special status field, an invoice download, a shipping detail, a credit, an account-specific view, a custom configuration, or a page that was never included in the integration.
Sometimes the business has access to an API but not the engineering capacity to implement it. Sometimes the integration exists but does not cover the exact workflow. Sometimes there is no usable API at all.
The portal becomes the universal fallback.
Humans have been the compatibility layer
The reason supplier portals “integrate” with every distributor is simple: a person can use them.
A person can sign in, navigate a changed layout, interpret the page, download the document, copy the status, and move the result somewhere else.
That human flexibility is powerful. It is also expensive when applied to hundreds of routine checks.
Screen-operating agents change the last-mile equation
An AI agent with a real browser and full desktop can work through the same approved interface an employee uses.
That means automation no longer has to wait for a custom connector before it can begin. The agent can be trained on the workflow: where to log in, what to retrieve, what to compare, what to update, and when to ask for help.
The important part is not “browser automation” by itself. Traditional scripts can also click a browser. The important part is combining visual operation with learned business rules and human escalation.
APIs and agents should coexist
If a reliable API can retrieve a field faster and more cheaply, use it.
If the rest of the workflow requires a portal, let the agent use the portal.
The architecture should be pragmatic. Businesses should not force every step through an LLM, and they should not leave a workflow manual just because one system lacks a clean integration.
The goal is completed work.
The portal is not going away soon
The industry's software ecosystem will keep improving. There will also always be long-tail suppliers, account-specific experiences, older applications, and workflows that sit outside the standard.
A company that can automate only the perfectly integrated portion of its business will still carry a large manual tail.
The ability to operate the screen makes that tail addressable.
AltOps gives each agent an isolated full desktop and teaches it to use supplier portals by sight and click, making workflows possible even when APIs are missing, incomplete, or not worth a custom integration project.
Sources: PromoStandards Tech Summit 2026 content; AltOps published product architecture; 2026 industry discussions around SanMar, S&S, SAGE, and cross-platform supplier workflows.
Written by Kavish Soningra, teaching agents to run the back office at AltOps.
