Price Levels (Standard)
Price tiers for every item, assigned to customers, synced from your ERP; as many as needed. Example: ITM1 in SAP B1, with equivalents in virtually any other ERP.
Across 150+ implementations we’ve codified the recurring shapes of distributor operations. Below is a working sample of the library across the domains we configure most. If your operation has a quirk that isn’t here, it usually joins the library after we ship it.
Every pattern below can be scoped by customer group, individual customer, item group, SKU, or any other attribute available in your ERP.
Price tiers for every item, assigned to customers, synced from your ERP; as many as needed. Example: ITM1 in SAP B1, with equivalents in virtually any other ERP.
Fixed agreed-upon special pricing for specific SKUs, for specific customers. Synced from special-pricing tables (e.g. OSPP in SAP B1, item pricing in NetSuite, and the equivalent in every other ERP).
Show the customer's last paid price and/or default to it, drawn from invoice history in the ERP. Optional floor blocks undersells and protects the margin if costs have risen.
Compute pricing dynamically: 0.9 × list, cost + 18%, target-margin floor, MSRP with a defined spread, etc, etc. Applied as broadly or narrowly as necessary. Formulas can be defined in ERP and integrated, or only in Pepperi.
Volume tiers built into the price itself, from ERP or defined solely within Pepperi. As many tiers as needed, with discount % or explicit unit price at each quantity tier reached.
Multi-jurisdiction tax (estimated or live, e.g. from Avalara), bottle deposits, environmental fees, freight surcharges, shipping fees (estimated or live from the carrier), all calculated on the cart in real time.
$X.99, $X.00, $X.X5, or any other rule, per-currency rounding. Defined globally or per product class.
Sell in any currency your ERP supports. Customer-default or per-order override as required.
Per role or per user: prices locked, prices modifiable within a % band (can vary by product), or fully wide open. Manual approval routings for edge cases, only when needed.
UOM ladders, parent-child inheritance, MAP enforcement, future-dated launches, approval-gated overrides, mixed formula and contract logic across product classes. Across 10 years of ERP integrations, we have yet to meet a pricing scheme we couldn't handle, and usually for much less budget than you might think. If yours is the (first) exception, we'll tell you before you sign anything.
BOGO, percent off this SKU, dollar off this SKU. Add the trigger item, the promo appears instantly. Drops back out if the cart changes.
Curate a set of products, define the threshold, choose the reward. The customer picks what qualifies, and when the reward is a free item, picks that too from a separate curated set. Example: Buy any 6 from this list, save 15%. Buy any 4, choose 1 free case from these 8 SKUs.
Total order $, or subtotal of just qualifying items, unlocks a discount or gift benefit. Unlimited tiers, let bigger carts earn bigger benefits, with rewards updating in real time as items are added.
Easily set promotions with pre-defined start and end dates, customer (attribute) inclusion / exclusion lists, or full manual control. Easily duplicate or re-publish past promotions.
Decide which promos combine, which override, which are mutually exclusive. Predictable math, every cart.
Multiple units of measure per item (each, inner pack, case, pallet) with a UI that shows only the UOMs available for that SKU. Quantities map back to the ERP in the unit your ERP expects.
Enforce minimum order quantities, pack quantities, case rounding, and item-level maximums. Per SKU, per customer, or per group. Violations blocked at entry, not at ERP post.
Multiple ship-to addresses per customer, synced from the ERP and selectable inline during order entry. Default address per customer, override per order, and/or allow one-off addresses keyed in the moment.
Add items to the order by scanning, using the device camera or a paired Bluetooth scanner. Speeds up large orders and counter-side replenishment.
App or web, iPad or laptop or phone. The system automatically recognizes screen size and presents an optimal view accordingly. Reps and buyers get the right layout for the device in their hand, with no separate setup.
Web and iPad localization driven by the customer's attribute. Item names render in the buyer's language, UI labels follow device locale.
Sorting, filtering, and searching, optimized and defined with any attribute from your ERP. Buyers and reps find the right SKU fast, even in catalogs that run into the tens of thousands. Online or offline.
Surface any inventory field your ERP exposes: on-hand, available, allocated, transfer-pending, PO-pending, plus any custom field. Show one field, several side-by-side, or a calculated sum.
Show only the warehouse the customer is assigned to, show all warehouses, or sum a defined subset. Refreshes faster than typical ERP exports.
Block overselling, allow it with a warning, or hide out-of-stock items entirely from browse and search. Behavior set per customer group, item group, or globally.
The visibility rules below can be scoped by customer, customer group, item attribute, or by user type (rep vs. buyer), and can either hide items entirely or simply prevent them from being added to the cart.
Define exactly which items a customer (or class of customer) is allowed to see. Useful for proprietary catalogs, private-label SKUs that only ship to specific retailers, channel-segmented assortments, and customers on a contract that limits them to an agreed-upon item list.
Hide or block specific items for specific customers. Useful for legal restrictions by region or license, discontinued items still cleared for a few accounts, recall holds, and competitor brand exclusions on shared distributor accounts.
For SKUs with variants (sizes, colors, flavors, pack configurations), enter quantities across the full grid in a single screen instead of clicking into each variant. Rows are one variant axis (e.g. style), columns are another (e.g. size); totals roll up live.
New-customer flow that round-trips to the ERP with External-ID timing handled, so the first order doesn't fail because the customer isn't in the ERP yet.
Per-customer notes, visit logs, and activity history, captured by reps in the field, visible to everyone on the account. Searchable, taggable, and round-tripped where the ERP supports it.
Overdue balances, aging buckets, open invoices, and full invoice history, pulled live from the ERP so reps know what's owed before they pitch the next order.
Connect any customer to the buyer self-service storefront in two clicks. Their pricing, their assortment, their ship-tos, already configured from the rep-side data. No second onboarding.
Every configuration and integration in this page applies equally to the buyer storefront. Pricing rules, promotions, item visibility, inventory logic, payment capture, all of it. Setting up the platform to work for your reps means your customers are ready to go when you are. One engine, two faces.
Set up a custom subdomain, a custom login screen, and a themed UI. Outbound emails sent from your own domain. Your customers experience your brand, not ours.
Native iOS and Android apps published under your brand to the Apple App Store and Google Play. Your icon, your name, your splash screen. Same buyer storefront underneath.
Order confirmation emails go out to your customers with a tailored confirmation PDF, with CC or BCC to everyone in your organization who needs to know. Sales reps, AR, warehouse, account managers; copy whomever the workflow demands.
Your customers see all of their past invoices and the current status of any order they're waiting for, pulled live from the ERP. Fewer calls to your customer service team, less back-and-forth on "where's my order."
Card and ACH processing with persistent customer profiles between orders. Mandatory or optional per customer; receipts and payment records written back to the ERP.
The van becomes its own warehouse. Van and warehouse stock visible side-by-side; orders decrement van first, then warehouse. While offline, between syncs, or all day in the field, Pepperi tracks decrements locally so each order knows what the previous ones consumed. Load-van transactions handle restock and visit tracking; reconciles to the ERP at end of day.
Review a submitted order at delivery and indicate quantities received line by line. Discrepancies between ordered and received quantities are counted automatically, ready for credit memo, adjustment, or follow-up.
Lists for orders, invoices, credit memos, and other transaction types, with smart filters, on-the-fly totals, and Excel export.
Custom analytics dashboards with direct Pepperi data access. Built around the questions your team actually asks.
Configure an automatically updating report of order history data and store it as a single, static link or CSV file on an FTP. Easy access from Tableau, Power BI, Looker, or any other BI reporting tool in your stack.
The library covers the recurring shapes across our practice, but every distributor has at least one quirk that doesn’t fit a standard mold, and most of those quirks join the library after we ship them. Bring us yours →
30 minutes. We ask first, then walk through which patterns drop in and which need shaping.