Skip to content

FousAlbertsonsNet for Suppliers

Turn AlbertsonsNet for Suppliers into an API

Read your AVISS tickets, with their state, request type and assignee, through one API call, or file a Short-Paid Invoice or Deduction request. A workflow can check the Ticket List View each weekday morning and email you the tickets that moved to Pending.

Works with your own AlbertsonsNet for Suppliers account. Fous is an independent product.

What you can build on the Albertsons vendor portal

  • Get AVISS tickets

    Build this

    Reads the Ticket List View in AVISS, linked from the vendor portal, filtered by State and request type when you give them.

    Takes
    State (optional), request type (optional)
    Returns
    Ticket number, date updated, state, request type, name of vendor, assigned to, description
  • Check one AVISS ticket

    Build this

    Finds one ticket by its number in the AVISS Ticket List View and reads where it stands: Submitted, Processing, Pending or Resolved.

    Takes
    Ticket number
    Returns
    Ticket number, state, request type, date updated, assigned to, description
  • Dispute a short-paid invoice in AVISS

    Build this

    Opens Submit a Request, chooses Short-Paid Invoice or Deduction, fills in the inquiry, attaches the invoice and proof of delivery, and submits it.

    Takes
    Inquiry type, vendor type, delivery location, invoice number, invoice date, amount, PO, payment number, attachments
    Returns
    Ticket number, state, request type

Automate the Albertsons vendor 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.

  • AVISS tickets waiting on you, every weekday

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Get the AVISS tickets in the Pending state.
    Step 2
    Keep the tickets that were not Pending on the last run.
    Step 3
    Email you the list with ticket number, request type, description and assigned to.
  • AVISS ticket state changes, to your deductions log

    Build this
    Starts
    Every day at 17:00
    Step 1
    Get all AVISS tickets from the Ticket List View.
    Step 2
    Keep the tickets whose state changed since the last run, and stop when there are none.
    Step 3
    Post each one, with its new state and date updated, to your 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 “Get AVISS tickets” 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": "partner.safeway.com/get_aviss_tickets",
    "input": {
      "state": "Pending"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "tickets": [
      {
        "ticket_number": "0048213",
        "date_updated": "2026-11-10",
        "state": "Pending",
        "request_type": "Short-Paid Invoice or Deduction",
        "name_of_vendor": "Acme Foods",
        "assigned_to": "Accounts Payable",
        "description": "Need to dispute a deduction or billing, invoice 77120"
      }
    ],
    "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 Albertsons vendor portal’s own options

Albertsons exchanges purchase orders, invoices, ship notices and payment remittances with suppliers by EDI, over a direct AS2 connection or your VAN. Its supplier pages document no API for the vendor portal's web tools: AVISS, the IDA reports and Webview schematics are used in the browser.

OptionWhat it coversWhat it takes
EDIPurchase orders (850/875), invoices (810/880), PO acknowledgments (855), ship notices (856), application advice (824) and EFT remittance (820).A Trading Partner Information form, Albertsons' implementation guides and test invoices reviewed by an EDI analyst and Accounts Payable.
The vendor portal by handLinks to AVISS for payment and deduction inquiries, Item Distribution Analytics (IDA) reports, Webview schematics, APEX and Specright.A vendor user ID in the form userID@safeway.com and its password.

Read on November 12, 2026: Albertsons EDI Practices, EDI Processing and Communications Schedule, Albertsons vendor portal.

Signing in to the Albertsons vendor portal

The vendor portal signs you in on an Albertsons Companies page headed Sign in with your organizational account, with your user ID in the form userID@safeway.com and your password. AVISS opens through a Microsoft sign-in page. With Fous you sign in once through the site's own sign-in with your own account: the login is sealed with AES-256, never returned by the API or written to logs.

Worth knowing

Each tool is its own site
The vendor portal links out to AVISS, the IDA reports, Webview, APEX and Specright, and lists separate support for EDI, IDA, Webview and Specright. A method you build works in one of these tools.
One purchase order per invoice
An invoice that references other purchase orders, even ones that shipped together, generates errors and has to be re-submitted. Several invoices for one PO are allowed with N9 'AI' references.
No corrected purchase orders
Albertsons sends only an original EDI purchase order and cannot re-transmit a corrected one. It can resend a transaction that was already sent.
EDI runs on Mountain Time
Purchase orders go out at 12:05 AM and then hourly from 2:05 AM to 10:05 PM, Mountain Time. Application Advice (824) for invoice errors is processed at 2:00 AM.

More in Retail: vendor portals (North America)

Other industries: REWE Group Supplier Portal, Verizon Enterprise Center, Gas Safe Register online services, Taulia supplier portal, Xero Practice Manager, Justdial for Business.

Frequently asked questions

Not for its web tools. Albertsons' supplier pages document EDI for purchase orders, invoices, ship notices and EFT remittance, over AS2 or your VAN, and no API for AVISS, the IDA reports or Webview, which you use in the browser.

File a Short-Paid Invoice or Deduction request in AVISS, choosing an inquiry type such as Need to dispute a deduction or billing. The invoice number is required, and the original invoice and a POD with an Albertsons Receiving stamp are the recommended attachments.

Submitted means Albertsons has the ticket but has not started. Processing means work has begun. Pending means it needs more input, usually from you. The fourth state is Resolved. The Ticket List View filters by state, request type and assignee.

No. Albertsons expects one invoice to contain items from one purchase order, and an invoice that references other POs generates errors and has to be re-submitted. Several invoices against one PO are accepted with N9 'AI' references.

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

Put AlbertsonsNet for Suppliers 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 nextCVS AP Vendor PortalHome Depot Supplier HubKroger Partner PassREWE Group Supplier PortalHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of AlbertsonsNet for Suppliers (Albertsons Companies). 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.