- DigitBridge Knowledge Base
- General
- Informative
-
PIM Module
-
Commerce Central Module
-
General
-
Troubleshooting
-
Settings
-
Inventory
-
Sales
-
Fulfillment
-
Purchasing
-
Accounts Receivable
-
Accounts Payable
-
Customers
-
Vendors
-
Dashboards
-
Warehouse
-
Content Management
-
Channel Management
-
Integration
-
QuickBooks
-
Import/Export
-
NEED CATEGORY
-
Returns
-
EDI
-
3PL
-
Dropship
-
Customer Portal
-
Manufacturing
Why would I use multiple multipliers or additions when updating prices?
Here's how layered pricing logic can help you fine-tune your strategy in DigitBridge.
DigitBridge’s Price Update tool supports up to three multiplier and three addition fields for each price update. This layered approach might seem excessive at first—but in complex pricing environments, it provides flexibility that a single step can’t match.
When would I need multiple multipliers or additions?
Here are a few examples where multiple fields come in handy:
-
Example 1: Handling fluctuating costs and margin targets
If your base cost has changed due to a material cost update, you might want to first multiply it by your standard margin (e.g., ×1.8), then add a fixed dollar buffer (e.g., +$1.50), and finally apply a channel-specific surcharge (e.g., +$0.25 for marketplace fees). -
Example 2: Layering regional or customer-type adjustments
Say you’re using MSRP as a base, but want to apply discounts for certain customer types. You might:-
Multiply MSRP by 1 (no change),
-
Subtract a loyalty discount in the addition field (e.g., -$2.00),
-
Then add a surcharge for freight (e.g., +$0.75).
-
-
Example 3: Temporary price adjustments or promotions
You can multiply your base by 1 to hold it steady, and then use the addition fields to introduce and later remove temporary incentives.
What if I only need one field?
That’s perfectly fine. If your pricing logic is simple—say, WSP = Cost × 2—just use one multiplier. The other fields can remain blank. DigitBridge will only calculate using the values you enter.
Tip: Use the multiplier fields first to apply percent-based logic (e.g., margins), and the addition fields to handle flat fees, adjustments, or rounding differences.
Related guides: