Set eligibility requirements

Eligibility requirements describe what a customer needs to qualify for an item. Meeting them does not confirm availability, reserve an item or grant approval.

How it works

Open Eligibility for a Catalog type or category. On an item, open Audience & Eligibility: eligibility requirements have their own section there, separate from who can see the item, what a customer already holds and what your team records about them.

Choose from age, time holding a licence, monthly income, country of residence and a document held. Enter the required value and the wording customers should see. Time holding a licence applies to any licence; say which one in the wording customers see, or add a document requirement for the licence itself. Monthly income includes its currency and always means income per month. Country choices currently cover Ghana, Nigeria and Côte d’Ivoire. Document choices are driving licence, passport, national ID, residence permit, professional licence, proof of address, birth certificate, student ID, proof of employment, business registration certificate and tax registration certificate; custom facts and documents are not supported.

To limit an item to a kind of customer, such as business customers only, use a contact profile field and a segment, then limit the customer action to that segment. Eligibility requirements are for facts a customer gives when they act.

A type supplies shared requirements. A category or item replaces a shared requirement only when it checks the same detail, comparison and unit. Document requirements replace only the same document. Other shared requirements remain. For example, an item’s minimum age replaces its category’s minimum age, while a shared maximum age or income requirement still applies. Removing an item requirement and publishing brings its shared requirement back. Requirements marked Always applies at lower levels remain in force when a category or item has its own requirements. Inherited requirements appear separately and cannot be removed there.

How to use it

1. Open the type or category settings and choose Eligibility, or open an item and choose Audience & Eligibility.
2. Under Eligibility requirements, choose Add requirement, choose what to check and enter its value. Choose whether lower levels may replace it.
3. Enter what customers should know. Make this match the requirement, such as “Drivers must be at least 21 years old.”
4. Save. On a type or category choose Save draft; on an item, use the editor's Save. A saved draft does not change the requirements customers use.
5. Choose Review and publish and check the exact requirements and inherited rules. Someone with Catalog publishing permission can confirm and publish them.

To get help drafting these requirements, save your changes and choose Ask Qyra at the top of the settings. Review the proposed draft before saving it; publication remains a separate step. Existing audience and relationship settings stay separate.

For example, a vehicle type can require a driving licence at every level. Economy vehicles can require a minimum age of 21; SUVs can require 25. A particular SUV can require 30 when its inherited age rule permits replacement. The shared driving licence requirement still applies.

When it does not happen

You have not published the changes: saved drafts stay private. Review and publish the draft before relying on it in customer checks. Choosing More > Turn off requirements here removes requirements from this level and inherited requirements that allow replacement. Inherited requirements marked always apply remain in force. Use shared requirements restores the normal shared requirements instead of turning them off.

The customer does not qualify: a confirmed answer may not meet a published requirement. Explain the requirement using its customer wording. A missing answer means the result is not known yet; it does not mean the customer failed the check.

Published requirements disagree: a shared minimum can exceed a category or item's maximum, or residence requirements may have no permitted country in common. Results stay unconfirmed while the rules conflict. Review the requirements at each level. Change an always-applicable requirement where it was originally set; a category or item cannot remove it.

Qcom could not confirm the requirements: an unavailable requirement source is not a rejection of the customer. Try again, or ask a workspace owner to check access. If someone changed the requirements while you edited, reload the latest version and review your changes again. Reloading asks before discarding unsaved changes.

A check or comparison explains the published requirements. Booking, an order or an application still makes its own final decision. Existing written Application requirements remain informational; they are not automatically converted into checks.

Customer checks and comparisons depend on the consuming tool being connected to these requirements; publishing alone does not enable those tools. Next, learn how to set up Catalog tools.

Older amount limits

Amount limits belong in Payment settings. If customer requirements still show old amount limits, review them and set the appropriate limits in Payment first. Then select Remove these old amount limits when I save this draft, save, review and publish the customer requirements. Old values are kept until you explicitly remove them; they cannot be published again as customer requirements.