List and tier
The buyer ID determines which master list and contract tier to unlock. Label price is not assumed.
gratisRENAULTDACIASTELLANTISPEUGEOTCITROËNOPELTOYOTALEXUSHYUNDAIHONDAVespaPiaggio
Short answer
What is a B2B pricing system?
Request a meetingThe B2B pricing system is a rules engine that calculates — directly from the record — who sees which price list, discount, payment term, and currency. It is not a catalogue label. It is not a promotional banner. Shopsoft connects this engine to the backbone of B2B software; it does not leave pricing to an Excel cell or a sales representative's memory.
In enterprise pricing, there is no such thing as 'the price of a product' — there is the price for a given buyer, a given contract, and a given moment. The same SKU can produce three different values for a dealer, a chain retailer, and an export customer. The Istanbul team, which has been developing software since 2004 and brings over 700 agency infrastructure engagements to this rules discipline, pursues a single objective: ensuring that the basket price and the dispatch price never diverge.
Business problem
A price discussion is not a product discussion.
In B2B sales, the breakdown is rarely caused by stock — it is caused by price. A dealer sees one figure on the portal, a sales representative recalls 'last month's discount', and finance prints a third amount on the invoice. Three versions of the truth coexist on the same day. Reconciliation becomes a battle at month end; customer confidence collapses before the next order is even placed.
As price lists multiply, the fragmentation becomes invisible. A master list, a regional list, a contract tier, a temporary promotion, a case-break breakdown, and a currency variant. One lives in a spreadsheet, one in the ERP, one in an e-mail attachment. It is never clear which one prevails. To retain the customer, the sales representative quotes a verbal price that no system records. By the time the shipment goes out, the dispute has already begun.
The second break is unauthorized visibility. A neighboring dealer sees the better list or does not, but says “I saw it.” The third break is the timestamp. If the price is not frozen at the moment of order, the rate or list will have changed by the shipping day. In discovery Shopsoft wants an open order and that order’s three price stories. If there is no story, the engine is not written.
This page does not take the order portal, purchasing tender, or inventory software as its primary target. The subject is for whom, at which moment, and under which rule the price is born. A campaign showcase does not carry this work. List price is a B2C habit; in B2B the tag is often a lie.
If the field team operates on "I remember the old discount" basis, there is no system. A remembered price is not the version of the contract. When a new tier is added, old orders must not be silently updated. If they are, historical revenue figures become unreliable. The engine calculates and freezes; it does not forget, and it does not write back into the past.
When exchange rates and taxes are recorded in a notes field, a second hidden system is born. Once an export operation or a second legal entity is added, the phrase "that is how we handled it back then" becomes mistaken for a rule. Global B2B platform deepens that layer; this page does not duplicate it. The rule here is this: currency and tax are part of the price record, not a footnote.
On the corporate purchasing system side, there is also a price: the purchase contract. If it becomes mixed up with the sales pricing engine, both the dealer and the supplier end up consuming the same rule. Shopsoft separates the sales list from the purchase tier during discovery. If you do not keep them separate, the discount leaks in both directions.
The Shopsoft approach
Calculate, display, freeze.
Shopsoft does not write the price at the top of the screen. First the rule layers are clarified: list, customer tier, quantity break, payment-term differential, temporary campaign, currency. Layer order is written in discovery. Without order, “lowest wins” chaos arises.
The approach has three steps. The engine calculates. The surface displays. The order freezes. Basket value and shipment value do not silently diverge. If it changes, it leaves a trail. Order management system carries the frozen amount; the price engine does not reinvent it on every shipment day.
Dealer management system scorecard reads the turnover; the pricing engine knows from which tier that turnover originated. It does not blindly distribute the target discount. Scorecard and engine are linked; they do not replace each other. CRM software can keep a “special price discussed” note; a note is not a list.
The Istanbul team does not run discovery like a discount negotiation. One open order, one contract, one “why this invoice is different” document is enough. In global work, the local communication network does not confuse language differences with rule differences. A translation pack does not generate prices.
Authorization defines which user can view which price list. A representative cannot browse an adjacent tier. The permission to freeze prices is a separate role. Shopsoft does not treat this filtering as menu concealment; it is a data partition. Opening a different price list via a direct URL is not permitted.
A campaign is a time-bound rule that is layered on top of a price list. Applying the same price band to all customers is not how the engine works. A customer who meets the campaign target and one who does not will not receive the same discount. When the period ends, the rule closes; there are no forgotten rows left behind in a spreadsheet. The engine ties the time window to the record.
Inventory management system does not generate prices. Inventory tells you which warehouse's stock has been committed; price tells you at what value that commitment will be closed. Both land in the basket at the same moment. Displaying a price when there is no stock is selling something that does not exist. The engine does not ignore stock; it does not steal the logic of your inventory software.
Going live does not have to mean every listing changes on the same day. The first slice closes the triad of master list + customer tier + price freeze. Campaigns and currency layers are added once that triad is solid. The reverse keeps verbal discounting alive behind an attractive price display.
Core capabilities
Places where the price must originate from the record.
This list is not the campaign module. These are the tasks that the B2B pricing system must carry as a rule.
Breakdown and maturity
Quantity, carton, and payment-term differentials are governed by rules. Representatives do not negotiate line by line; exceptions leave an audit trail.
Campaign layer
A time-limited rule overrides the top of the list and does not apply uniformly to everyone. It closes when the period ends.
Currency and tax
Exchange rates and tax are not footnotes. They appear in the heading; they produce no surprises on the day of dispatch.
Freeze
The value at the moment of order is preserved. The cart and invoice do not silently diverge.
Audit trail and versioning
Who changed which list is recorded in the log. Retroactive writing is the lie of turnover.
Operational scenario
Morning list, midday cart, evening same amount.
The new tier takes effect in the morning. The dealer in Anatolia opens 18 items from the portal. Carton breakdown drops on three items, a time-limited campaign is added on one item, and the term difference is clarified. The basket total is the rule of that moment. The representative does not call; “let’s apply the old price” is not recorded.
At noon the limit threshold holds one line in draft. Even if the price is correct, the current account cuts it. In the evening the warehouse dispatches. The invoice is generated from the frozen line amounts. Even if the exchange rate has changed, the order moment is stored. The customer does not say “the invoice is different”; they would have to if there is no trace.
Same day an exception is requested. The person with the role changes the line and writes the justification. A log is kept. At month-end the question “who gave this price?” does not land on the phone. Dealer management system sees this turnover’s tier on the scorecard; speculation ends.
The export customer opens from the foreign-currency list. The currency is in the header. The translation package does not generate a price. Shopsoft in discovery plays this morning with your list count and tier depth. Four lists and forty lists are not the same engine; the rule order changes.
Applying the same tier to everyone on a campaign day generates queues and disputes. The engine opens the rule to the tier that meets the target. The tier that does not meet it sees a label. This is not a marketing automation promise — it is the result of price recording.
When a contract is renewed, the tier is versioned. Existing open orders do not silently migrate to the new tier. A new order receives the new rule. Without this distinction, historical revenue is corrupted and future pricing disputes arise. The engine knows both points in time.
How it works
Rule order first, then the screen.
Drawing up a pricing screen is not the same as building the engine. When layers collide, the software bloats before it becomes clear which one wins.
Request a meeting-
Layer map
The list, tier, breakdown, campaign, exchange rate, and tax sequence are extracted. Conflicting Excel files are brought to the table.
-
Authorization section
Who sees which list and who changes the frozen value. Set up in filtered data.
-
Calculate-display-freeze
The engine calculates, the surface displays, the order freezes. If the three steps become disconnected, disputes arise.
-
Version and exception
The new tier is versioned. The exception leaves a trace. The first slice closes this discipline.
Integrations
Price does not generate a second source of truth.
API integration carries the list and tier into the ERP or accounting close. Blind copying generates a second price. The order carries a frozen value; the ERP must not recalculate on every shipment day. Which party holds authority is a discovery decision.
The portal and the field query the same engine. If two surfaces speak to two lists, there is no B2B pricing system. The order management system binds the frozen amount to the invoice. Inventory actuals confirm which goods the price speaks to.
The purchase side is a separate rule. The purchasing tier does not leak into the sales list. Shopsoft distinguishes in discovery which event is instant calculation, which is queue, and which is human exception. There is no fixed stack.
Marketplace or EDI price can be mapped to the B2B tier. Conversion loss is not accepted as “approximately held”. If the line does not match, it remains in draft. This page does not primarily target the marketplace product; it explains that the engine rejects blind matching.
The exchange rate service does not have to be the same across every project. The rate is part of the record; when the external service is disconnected, the value captured at the time of the order persists. A live rate must not corrupt the invoice on the dispatch date. This is precisely why rate freezing exists.
A CRM opportunity amount is not a price record. A quotation must originate from the engine's current rule set; it must not be entered into a notes field. Otherwise, the winning opportunity becomes the losing invoice.
Business benefits
The closed deal is three prices coming down to one price.
| Name | When there is no engine | With B2B pricing |
|---|---|---|
| Visible price | Field remembers | From tier record |
| Cart | Label or Excel | The rule of the moment |
| Shipment / invoice | Third amount | Frozen row |
| Campaign | Same SMS to Everyone | Time-limited tier |
| Exception | Verbal approval | Tracked change |
| Exchange rate / tax | Notes field | Record in header |
Technical approach
Rule order, not theme.
The technical core is the rule layers and the order-moment freeze. If the layer sequence is ambiguous, the engine resolves differently each time. The log retains which layer was applied on that line. This is a design principle, not a promise of any specific rule engine product.
The version is the timeline of the list. Retroactive writing is the lie of turnover. An open order does not silently migrate to a new tier. The draft stores the calculation moment or recalculates when the period expires; this is written during discovery, not assumed.
The permission scope is a list. A representative cannot browse an adjacent tier. Price-freeze authorisation is a separate role. Another contract cannot be opened via URL. Infrastructure is discussed according to list volume and account frequency. The same cached product is not imposed on every project.
Rounding and case-break rules are mandatory, not decorative display elements. A penny discrepancy becomes a reconciliation dispute at month end. The engine records unit conversions. An Excel formula cannot carry this workload.
An exception is contained within the rule. The WhatsApp exception is the second list. If there is no justification, role, or duration, there is no exception. Shopsoft does not accept the statement "we always build custom" during discovery without supporting documentation.
Performance does not mean scanning the full catalogue at the moment of cart. The buyer segment is filtered first, then calculated. This is a design preference, not a specific database commitment. Volume is discussed during discovery.
Security, scale, governance
Discount is a trade secret.
The list and tier structure are trade secrets. Access is governed by permissions. A dealer cannot view a neighbouring dealer's contract. A representative does not browse the entire network by default. Hiding menu items does not prevent data leakage.
The change log cannot be deleted. Who modified a tier and who wrote an exception are recorded in the log. Personal and commercial data are handled in accordance with KVKK discipline; document numbers are not fabricated. ISO references are not written before certification is confirmed.
Scale refers to concurrent basket and seasonal campaigns. The campaign day must not disrupt the rule order. Dead campaigns must not lock stock or price. The duration rule is rewritten from scratch.
Shopsoft is headquartered in Istanbul. In the global listing, language, currency, and tax appear in the header. There are no confidential case studies or penetration testing commitments. Backup and disaster recovery scenarios are determined according to project requirements.
The section of the departing representative is closed. The shared password is the leak of the neighbour list. The role is bound to the assignment. This rule does not primarily target the SSO product; the price record is the authority fact.
When a new company or new country is added, the list multiplies; the order identifier does not multiply. The engine adds rules, it does not generate a second Excel file. Global B2B platform deepens this growth; this page does not take it away.
Decision criteria
Pricing engine or pricing spreadsheet?
Three prices
Is the portal, field, and invoice each telling a different story at the same time?
Freeze
Is the shipment day changing at the moment of order?
Leak
Does it open with the adjacent tier URL?
Trace
Is it in the exception log or on WhatsApp?
Common mistakes
Mistaking the label for the B2B price.
The first mistake is exposing the consumer label to the dealer. There is no tier separation. The second mistake is having every line manually marketed by a person. The engine stalls. The third mistake is never freezing prices at all. Set them on dispatch day and the list drifts.
The fourth mistake is treating the pricing module as inventory software. Inventory makes promises; pricing calculates the close. This page does not replace your inventory product. The fifth mistake is treating a CRM note as a price list. The sixth mistake is pushing a campaign to everyone. The seventh mistake is confusing the purchase tier with the sales tier.
The eighth mistake is writing backwards. Historical turnover lies. The ninth mistake is not writing the rule order. When layers collide, the chaos of "lowest wins" is born. The tenth mistake is keeping an exception alive without documentation. WhatsApp is the second list.
Scope of this page
Pricing records are described; cart and gradebook are not covered.
This page describes the B2B pricing system as a rules engine that generates value from the buyer + contract + moment triad. The B2B software is the backbone, the dealer portal is the surface, the order system carries the frozen amount, purchasing is the acquisition tier, and the global platform writes the currency and country to the header. The connection is visible here; it does not deepen as a primary objective.
The list price is not the B2B price. If three amounts coexist on the same day, there is no engine. Without freezing, a dispute on the day of dispatch is inevitable. Shopsoft requires one open order and three pricing narratives during discovery. Without the narratives, no rules are written.
The package and pricing CTA is not published. Discovery is free of charge. The TR version is published; EN and AR remain noindex. Internal links are not broken by placeholder pages. Images are sourced from the existing asset library.
This engine is intended for sales networks experiencing tension between list prices, tier pricing, and verbal discounts. Users seeking consumer campaigns, actual stock levels, or order status should navigate to the relevant page. Shopsoft reviews conflicts in existing Excel lists during the discovery phase. The consultation is free of charge; there is no package schedule.
The engine originates from the backbone. B2B software carries the record. Dealer management reads the tier from the scorecard. Purchasing separates the direction of acquisition. The global platform writes to the dry header. The API moves the list to the ERP. Stock confirms the promise. The order freezes. CRM keeps the note. Intentions do not mix.
The reader must distinguish the following: a cell is not a rule. Memory is not a version. A campaign does not reach everyone in the same way. An exception cannot exist without leaving a trace. Shopsoft draws this engine with your document. Discovery is free of charge. EN and AR remain noindex.
The final question has three consistencies to check. Are the portal, field, and invoice quoting three different prices simultaneously? Does the shipment date change between the moment of order and dispatch? Does an adjacent tier open via URL? Is the exception in the log or in WhatsApp? The answers should be in the record, not in a spreadsheet. In the Shopsoft discovery session, these layers are examined together with your order.
Valid since 2004, covering 700+ agency infrastructures and the Istanbul headquarters. Nothing is written before ISO approval. The CTA is Request a Meeting. There are no demos or pricing. Responses are provided within an average of 24 hours during business hours. One open order and one 'invoice discrepancy' document are sufficient to initiate a discovery session.
The engine calculates, the surface displays, the order freezes. The layer sequence is hard-coded. The exception leaves a trace. If these three sentences do not hold, what you have is a pricing spreadsheet, not a B2B pricing system.
Trust and references
A claim without documentation doesn't hold water.
Established in 2004, with 700+ agency infrastructure; Istanbul headquarters applies. Nothing is written without ISO approval. Logos may be used; confidential tier and discount tables are not published.
Discovery is complimentary. There are no packages. The meeting covers one open order, one contract, and one "three-price" story.
The required documents are concrete: a list, a tier, an invoice discrepancy. Shopsoft does not name competitors. The decision is whether the cart and the invoice carry the same frozen value.
FAQ / AI Answer Blocks
Clear answers about the B2B pricing system.
What is the B2B pricing system?
It is a rules engine that calculates, from the account record, which price list, discount, payment term, and currency each customer will see. Shopsoft configures this as calculate–display–lock.
Isn't the ERP price list enough?
It can be. In most networks, the list price sits in the ERP, the discount in a spreadsheet, and the exception in a phone call. The engine eliminates this fragmentation and locks in the price at the moment of order.
Is it the same as campaign management?
No. A campaign is a time-limited layer. The engine is the backbone of list management, tiering, and freezing. A campaign does not go out the same way to everyone.
Does the price change after the order is placed?
The frozen value is stored. If it changes, a trace is left. The cart and the invoice do not silently diverge.
Is the purchase price also governed by this engine?
No. The purchasing tier is a separate intent. If they become mixed, both the dealer and the supplier end up subject to the same rule. The link becomes visible; the primary target is not affected.
Is the discovery call paid?
It is free of charge. Responses are provided within an average of 24 hours during business hours.
Does the exchange rate distort the invoice every day?
It should not. The currency is set in the header; the rate is frozen at the moment of order. A live rate does not produce a surprise on the shipment day.
Can a representative grant a custom price?
If the role and justification exist, a tracked exception is opened. Verbal discounts are not entered into the record. WhatsApp is not a secondary price list.
Why does the neighbouring dealer see a different price?
It is tiered authorisation filtering. Each party sees only what they are entitled to see. A different contract cannot be opened via URL manipulation. Price leakage distorts competition.
Related Shopsoft solutions
This spine does not stand alone.
The pages below share the same sales, stock and integration truth. Continue from the bottleneck that is yours.
B2B
What is B2B software?
B2B software is the enterprise system that unifies company-to-company sales: order, stock, price, account and permission on one backbone. It does not beautify a storefront; it makes dealers, distributors and headquarters
See details
Global B2B Platform
Global B2B Platform
A global B2B platform is the sales backbone that carries language, currency, tax, delivery country, and local compliance rules within the same order record.
See details
Dealer Management System
Dealer Management System
A dealer management system is the backbone that keeps every dealer's targets, visits, order discipline, points, and closures running in a single record across your sales network. It is not a portal screen.
See detailsFree discovery call
Let’s clarify your software need in 15 minutes.
B2B, ecommerce or custom software — we listen to the operation and draw the right architecture together. Not a sales pitch; a working session on what the project actually needs.
- The discovery call is free and not a binding offer.
- We typically reply within one business day.
- No package SKU; architecture follows your company.
Start now
Request a meeting
Leave the form and the right team will reply. WhatsApp is also open — use whichever is faster.
Controller: Seo Software Danışmanlık Eğitim Telekomünikasyon Sanayi ve Ticaret Limited Şirketi. We use your details only to answer this request; marketing needs a separate opt-in.