---
title: Offer Management
slug: shkp-ajo/offer-management
docTags: 
createdAt: 2026-01-21T08:16:12.088Z
---

## Extending the Offer Schema

The offer schema can be extended to support custom fields, these will be used for storing information like what content should be displayed - eg. a title and description and banner image as well as any other custom meta data which might be used to influence eligibility or ranking.  For example if an offer is applicable for a specific mall or category, a ranking formula might boost the priority of this offer for customers with the same preferred mall or category.    

Offer attributes can also be used to create separate collections - the 

This is managed via the UI through **Decisioning -> Catalogs -> Offers.  **

Click to **Edit Schema.   **Unlike the schema's we created before this schema comes out of the box and is not related to the customer in any way.   From here you can modify the schema to extend the object.  

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/aQf_wdvnjzx4Ps69ZVKQ3_image.png)

You can see the custom fields added under the **\_demoapac **tenant. 

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/wt-tXIRf3aRjSugQpyvis_image.png)

## Offer Management APIs

The offer catalog can be fully managed via APIs you can review the API reference documentation here [https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/experience-decisioning-api-reference/getting-started](https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/experience-decisioning-api-reference/getting-started)

The postman collection shared contains an example call to **List**, **Create** and **Update** offers.