Suger

FAQ

Frequently asked questions about selling on Oracle Cloud Marketplace with Suger.

Which listing types are supported?

SaaS listings (package type SAAS) only. Other Oracle Marketplace listing types — container images, machine images, stacks, and Helm charts — are not synced and cannot be used in offers created through Suger.

Which pricing models are supported for private offers?

A one-time total contract value in USD for a fixed contract duration (6 months to 3 years). Installment plans and usage/metered pricing are not supported on Oracle Cloud Marketplace offers created through Suger.

Can I report usage charges for Oracle entitlements?

No. Oracle Cloud Marketplace private offers through Suger are one-time contract value only, so there is no usage metering to report.

How often does Suger sync with Oracle?

Automatically, every hour: listings, private-offer statuses, and derived entitlements are refreshed for every connected Oracle integration. You can also trigger a sync on demand from the Integrations page — for example, right after a buyer tells you they accepted an offer.

Does Suger import Oracle disbursement or payout reports?

Yes. Suger imports disbursement report records from the Oracle Marketplace Publisher API and converts them into revenue records, so Oracle payouts appear in Suger’s revenue reporting alongside your other marketplaces. Note that Oracle only exposes roughly the trailing 3 months of disbursement data; Suger persists every imported record, so your history accumulates in Suger beyond Oracle’s window, but backfills older than ~3 months cannot fetch anything new from Oracle.

What are the contract document (EULA) requirements?

The contract must be a real PDF file of at most 1 MB. If you provide it as a URL, the URL must be https. Other document formats (e.g. Word) are not converted automatically — export them to PDF first.

Why does my offer stay in “Pending Create”?

Suger sends the offer to Oracle and waits up to ~5 minutes for Oracle to confirm. If confirmation doesn’t arrive in time, the offer stays in Pending Create. Re-submitting is safe: if the offer actually went live in Oracle, Suger adopts it instead of creating a duplicate; if it’s a stale draft or a failed send, the old one is cleaned up and a fresh offer is created.

Why did the integration verification fail?

The most common causes:

  • The IAM service user lacks Marketplace Publisher permissions — check the policy statements.
  • Wrong region or compartment OCID.
  • The user or API key was created moments ago — OCI can take ~2 minutes to replicate new credentials. Wait and retry.
  • The private key is passphrase-protected — encrypted PEM keys are not supported. Generate a key without a passphrase.

How do I rotate the API signing key?

Add a new API key to the service user in the OCI Console, then edit the integration in Suger and paste the new private key and fingerprint. Leaving the private key field empty keeps the existing key.