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

1. The Problem

You update this property:

yacceleratorstorefront.quick.order.rows.min=6

After saving in hAC:

• UI shows 6 rows ✅

But after restarting server:

• Value goes back to 3 ❌

2. Why This Happens

SAP Commerce has multiple layers of configuration.

Two important ones:

1. hAC (Runtime Configuration)

• Changes applied instantly
• Stored temporarily
• Lost after restart

2. local.properties (Persistent Configuration)

• Stored in file system
• Loaded at server startup
• Persists across restarts

3. hAC vs local.properties (Key Difference)

FeaturehAClocal.propertiesPersistence❌ Temporary✅ PermanentRestart Required❌ No✅ YesUse CaseTesting / debuggingProduction config

4. Correct Way to Fix the Issue

Step 1: Identify Property

yacceleratorstorefront.quick.order.rows.min=6

Step 2: Add to local.properties

Go to:

hybris/config/local.properties

Add:

yacceleratorstorefront.quick.order.rows.min=6

Step 3: Restart Server

👉 After restart:

• Value remains 6 ✅
• Change is permanent

5. Where Does Default Value Come From?

Default value (e.g., 3) comes from:

project.properties

👉 Important:

• This is part of OOTB code
• Should NOT be modified

6. Why Not Modify project.properties?

❌ Problems:

• Overwritten during upgrades
• Not environment-specific
• Hard to maintain

✅ Best Practice:

• Override in local.properties

7. Configuration Priority (Important Concept)

SAP Commerce follows priority:

1. local.properties (highest priority)
2. Extension project.properties
3. Platform project.properties

👉 That’s why your override works when placed correctly.

8. Real Developer Mistakes

❌ Updating only in hAC
→ Works temporarily

❌ Editing project.properties
→ Lost after upgrade

❌ Not restarting server
→ Changes not applied

9. Bonus: Creating Properties Dynamically

You can also create new properties:

Via hAC:

• Add key + value
• Temporary usage

Permanent:

• Add to local.properties

10. Real-World Insight

In real projects:

• Developers test via hAC
• Final config goes into local.properties
• DevOps manages environment-specific values

11. Best Practices

• Always persist important configs in local.properties
• Use hAC only for testing
• Never modify OOTB property files
• Document configuration changes

Conclusion

If your Quick Order changes are not persisting, the issue is not with SAP Commerce—it’s with where you’re saving the configuration.

👉 Use hAC for quick testing
👉 Use local.properties for permanent changes

Understanding this difference will save you hours of debugging.

What’s Next?

👉 Next: SAP Commerce Quick Order Not Working? Common Issues & Fixes