Suger is now Fours. Read the announcement
Customers
Pricing
Insulin
Sign in Get a demo

Every marketplace purchase, one procurement record.

Requests, offers, entitlements and invoices for everything your organization buys, on the side of the transaction that spends the money.

See Fours in action Read the docs
The Fours buyer service console: a marketplace purchase as one procurement record, with its vendor, offer, entitlement and invoice together.

Illustrative sample data — not customer results.

Every team that buys, one system of record.

Make marketplace procurement a procurement decision, not an IT decision. Most of the friction sits between those two groups. A record all four can read takes it out.

Procurement & sourcing

Own the vendor list, raise purchase requests, and keep contract records straight.

IT & application owners

Know which entitlements are live, who they belong to, and when they end.

Finance & approvers

See what an offer commits the company to before signing, then follow the invoices it generates.

Cloud & FinOps leads

Watch marketplace spend and commitments in one place instead of per-vendor portals.

One transaction record vendor to invoice
Procurement & sourcing already works here
Zip Coupa Your intake workflow

Connecting these to the marketplace record is in development. Talk to us about being a design partner

A purchase, end to end.

Pick a stage to see what it touches. The orange label on each box is the module doing that work.

The seven modules, grouped by the stage that uses them

Finding a vendor, accepting an offer, holding an entitlement, paying the invoice.

Requests route through your own approvers, and the terms are read before anyone signs.

Charges sit against the entitlement that produced them, and roll up to one spend view.

The purchase Requests and approvals Outcomes Vendor discovered on AWS Vendor Offer accepted terms read before signing Offer and Entitlement Entitlement held against the vendor Offer and Entitlement Invoice paid charge, invoice, status Invoice and Payment Request raised what, and from whom Request and Task Your approvers internal workflow Request and Task Renewal offer comes back for review Offer and Entitlement Declined terms rejected Offer and Entitlement Spend view commitments in one place Home
Vendor
  • Discover vendors and products on AWS Marketplace
  • Keep the ones you buy from in one directory
  • Collaborate with the vendor in-product, not over email
Offer and Entitlement
  • Offers queue where the people who need the terms see them
  • Accept or decline where it was reviewed
  • Manage entitlements once an offer is accepted
Request and Task
  • Requests capture what is bought and from whom
  • Route through your own approval workflow
  • One queue for every open request and task
Invoice and Payment
  • Charges followed across every vendor
  • Invoices held against the entitlement behind them
  • Payment status without asking for a statement
Home
  • Spend in aggregate, not per vendor
  • Commitments visible before the next signature
  • Offers, requests and invoices awaiting action
Also in Buyer Service
Quick Guidehow the pieces fit, and the order to set them up in
Buyer Journeythe end-to-end path a purchase takes

Every module is documented in the Buyer Service documentation

Marketplace buying does not have to sit in a silo.

When a purchase goes through a marketplace, the person who owns procurement usually loses sight of it. No record to recognize, nothing to raise a purchase order against.

Today
Procurement works in Zip or Coupa Direct spend is visible and controlled
The marketplace purchase bypasses it No intake, no approval trail
Finance cannot recognize the spend Nothing to cut a purchase order against
Spend surfaces when the invoice lands
With Fours
One view across both Direct invoices and marketplace purchases in a single pane of glass
Requests route through your approvers The same workflow you already run
Every purchase has a record Terms, entitlement and invoice against the transaction that created them
One record, from request to invoice

Which end of the offer are you on?

300+ ISVs run listings on Fours and $10B+ has passed through it. Every one of those transactions had a buyer on the other end.

You are buying You are here

You receive offers, approve them internally, hold the entitlements and pay the invoices. That is this page.

You are selling

You build the offer, set pricing, and route it for approval before it reaches a buyer.

See private offer software for sellers

You are tracking the contract

An accepted offer becomes an agreement on both sides. Sellers manage theirs in Agreements.

See marketplace agreement management

Customer outcomes

More partner-driven growth.
Less operational drag.

Marketplace revenue, co-sell referrals and partner programs, run by teams who moved off spreadsheets and portals.

See all customer stories

Frequently asked questions

From procurement, finance and sourcing teams.

Which marketplaces does it cover?

AWS Marketplace only. Purchases made through Microsoft, Google Cloud or any other marketplace are not covered today.

Who in the organization uses it?

Procurement raises and tracks requests, finance reviews offers and follows invoices, application owners watch entitlements, and approvers sign off.

Does a purchase draw down our AWS commitment?

That is governed by your agreement with AWS, not by Fours. What you get here is visibility: spend and commitments on one dashboard before the next signature.

Why does a seller’s platform have a buyer product?

Fours sells to software vendors. This is the counterpart for the organizations buying from them, on the same transaction from the other side.

Bring marketplace buying
under one roof.

Thirty minutes on how procurement, finance and IT would run it from a single record.

See Fours in action

AWS Marketplace purchases