SCsapcommercejobs
Blogsap commerce cloud

sap commerce cloud

How Quick Order Works in SAP Commerce Cloud (Complete End-to-End Flow)

Quick Order is a powerful feature in SAP Commerce Cloud that allows users to add multiple products to the cart quickly using product codes or SKUs. It is widely used in B2B scenarios where speed and efficiency are critical. In this article, we’ll break down how Quick Order works internally—from configuration to backend logic and UI behavior.

Av
Avinash Jadhav

May 1, 2026•2 min read

1. What is Quick Order in SAP Commerce?

Quick Order enables users to:

  • Enter product codes directly
  • Add multiple products in bulk
  • Skip browsing and speed up checkout

Example Use Case:

A B2B customer already knows product SKUs and wants to place an order quickly without navigating the entire catalog.

2. High-Level Flow

Here’s how Quick Order works:

  1. User opens Quick Order page
  2. UI displays multiple input rows
  3. User enters product codes
  4. System validates product codes
  5. Products are added to cart
  6. User proceeds to checkout

3. Configuration-Driven Behavior

One of the key strengths of SAP Commerce is that Quick Order is configuration-driven.

Example Property:

yacceleratorstorefront.quick.order.rows.min=3

👉 This property controls:

  • Minimum number of input rows shown in UI

4. How Configuration Impacts UI

If you change:

yacceleratorstorefront.quick.order.rows.min=6

👉 UI will now show:

  • 6 input rows instead of 3

This demonstrates how SAP Commerce:

  • Uses configuration to control UI behavior
  • Avoids hardcoding values

5. Backend Logic (Java Layer)

The flow in backend:

  1. Property is defined in configuration
  2. Java class reads property value
  3. Value is passed to frontend (JSP / controller)
  4. UI renders based on that value

👉 This makes the system:

  • Flexible
  • Reusable
  • Easy to customize

6. Where is This Property Used?

You can:

  • Search property key in codebase
  • Find usage in storefront controllers or facades

Typically used in:

  • Controller → reads config
  • Model → passes data
  • JSP → renders UI

7. Temporary vs Permanent Changes

Change via hAC:

  • Go to: hAC → Configuration
  • Update property

👉 Behavior:

  • Works immediately
  • Lost after restart

Permanent Change:

Add in:

hybris/config/local.properties
yacceleratorstorefront.quick.order.rows.min=6

👉 Behavior:

  • Persists after restart
  • Recommended approach

8. Why Not Use project.properties?

If you update:

project.properties

👉 Problem:

  • Changes lost during upgrade

✅ Best Practice:

  • Always use local.properties

9. Real Insight: How SAP Commerce is Designed

Quick Order is a perfect example of:

👉 Config-driven architecture

Steps:

  1. Define configuration property
  2. Read property in Java
  3. Use value to drive UI

This pattern is used across SAP Commerce:

  • Checkout
  • Cart
  • Promotions
  • CMS

10. Common Issues

❌ Rows not updating
→ Property not in local.properties

❌ Changes lost after restart
→ Updated via hAC only

❌ UI not reflecting change
→ Server restart required

11. Best Practices

  • Keep UI behavior configurable
  • Avoid hardcoding values
  • Use local.properties for persistence
  • Document custom properties

Conclusion

Quick Order in SAP Commerce Cloud is:

  • Simple on the surface
  • Powerful under the hood

It showcases how SAP Commerce:

  • Uses configuration to control behavior
  • Separates logic from UI
  • Enables easy customization

What’s Next?

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

Related Resources