How to Configure Quick Order in SAP Commerce Cloud (Step-by-Step Guide)

1. Understanding Quick Order Configuration

Quick Order behavior is controlled using configuration properties.

Instead of hardcoding values, SAP Commerce allows you to:

• Control UI elements
• Define limits
• Change behavior dynamically

2. Key Quick Order Property

The most important property:

yacceleratorstorefront.quick.order.rows.min=3

👉 Controls:

• Minimum number of rows displayed in Quick Order UI

3. Step 1: Change Property via hAC (Temporary)

Steps:

1. Go to hAC (Hybris Administration Console)
2. Navigate to: Platform → Configuration
3. Search: quick.order.rows.min
4. Update value (e.g., 6)
5. Save

yacceleratorstorefront.quick.order.rows.min=6

Result:

• UI updates immediately
• Shows 6 rows

⚠️ Limitation:

• Change is temporary
• Lost after server restart

4. Step 2: Make Configuration Permanent

To persist changes:

Go to:

hybris/config/local.properties

Add:

yacceleratorstorefront.quick.order.rows.min=6

Result:

• Value persists after restart
• Recommended production approach

5. Why Not Use project.properties?

You may find this property in:

project.properties

⚠️ Problem:

• Changes get overwritten during upgrades

✅ Best Practice:

• Always override in local.properties

6. How Configuration Affects UI

Flow:

1. Property defined in configuration
2. Java reads property value
3. Value passed to frontend
4. UI renders rows dynamically

👉 This is how SAP Commerce achieves:

• Flexibility
• Reusability
• Maintainability

7. Verifying the Change

After updating:

• Restart server (if using local.properties)
• Open Quick Order page
• Check number of input rows

8. Debugging Tips

If changes are not reflecting:

• Check property spelling
• Ensure it's in local.properties
• Restart server
• Clear cache if needed

9. Creating New Quick Order Properties

You can also create custom properties:

Via hAC:

• Add new key-value pair
• Works temporarily

For permanent usage:

• Add in local.properties

Example:

custom.quick.order.limit=10

10. Real-World Insight

In enterprise projects:

• Business teams request UI changes
• Developers implement via config
• No code deployment needed

👉 This saves time and reduces risk

11. Best Practices

• Use meaningful property names
• Keep all overrides in local.properties
• Avoid modifying OOTB files
• Document custom configurations

Conclusion

Configuring Quick Order in SAP Commerce Cloud is simple yet powerful. By leveraging configuration properties, you can control UI behavior dynamically and build flexible applications without touching core code.

What’s Next?

👉 Next: Why Quick Order Changes Don’t Persist in SAP Commerce (local.properties vs hAC Explained)