Integration Patterns
Publisher Commerce integration patterns answer one question: where does the buy UI render? Two patterns cover the common shapes.
The two patterns
Embedded Buy Button
Buy Now buttons inline with the article. Checkout renders in a slide-in panel without taking the reader away from the article.
Dedicated Landing
Buy Now routes the reader to a separate landing page where the full checkout completes — useful when the publisher prefers a dedicated shopping experience.
How to pick
| If… | Pick |
|---|---|
| Reading-flow continuity is the priority | Embedded Buy Button |
| Publisher prefers a dedicated shopping page (separate brand or fuller PDP) | Dedicated Landing |
| Article references multiple products (roundup, gift guide) | Embedded Buy Button (cart accumulates across the article) |
| Single product with rich detail (long-form review) | Either — Embedded Buy Button for inline; Dedicated Landing for a full PDP shopping experience |
For which use case pairs with which pattern, see the mapping on Use Cases → How use cases relate to integration patterns.
The shared platform
Both patterns use the same Firmly API surface — auth, cart, checkout, payment, order placement. What varies is where the UI renders relative to the article.
Related
- Single Product Purchase Flow
- Multi-Product Purchase Flow
- Use Cases
- Agentic Commerce → Integration Patterns — the broader 4-phase matrix applicable across solutions