Price change approval: how to commission an online store integration

Price change approval: how to commission an online store integration

A manager has approved a new price list, but by evening the website is showing old prices and the cart is adding a discount that was not included in the calculation. The team is reconciling spreadsheets manually again. For a store owner, price change approval in this situation is a separate website development task: the responsible person's decision must be tied to specific data, and the customer must see the exact terms that were approved.

Do not commission only the uploading of prices from a file or an external service. You need a clear workflow: receive a proposal, check the rules, approve its version, apply it and reconcile the result. The proposal may come from an ERP, the enterprise's business management system, an ordinary spreadsheet or an artificial intelligence service. None of this removes the need to control publication.

Identify where the price originates and who authorizes changes

Start your conversation with the contractor by discussing the current process. Who sets the base price? Where are customer-specific price lists stored? Who launches promotions? Can a manager manually correct a value on the website? If the answers point to several systems, first agree on which is authoritative for each type of price. Otherwise, integration will merely transmit conflicting decisions faster.

A single source of approved prices does not necessarily mean one application for the entire business. The ERP may maintain the base price list, while the store manages promotional rules. What matters is defining the boundaries: exactly what each system is allowed to change and how the website calculates the total. Manual intervention also needs a reason, a responsible person and a rule for returning to the normal exchange process.

If a provider offers AI recommendations, separate its calculation method from web development. The business sets the objectives and permissible terms; the integration delivers data and applies authorized changes. A correct exchange does not prove that the recommended price is the best one or will generate more profit.

If your existing tools already support the necessary roles, checks and history, configuring them and refining the exchange may be enough. Commission a new component to address a specific gap, not because of a service's name.

Replace a spreadsheet row with a record of a specific change

The implementer needs to understand exactly what a person is approving. A button next to a generic “Update price list” label is of little help when the products, currency or validity period in the file have changed. Propose a change record containing the product or group, current and proposed values, sales channel, effective start, source and explanation. Product variations need an exact SKU, not just a model name.

Add the input data version and check results to the record. Approval must apply to this particular proposal. If a different amount arrives afterwards, the product list expands or important terms change, this is a new decision to make. Design a return to review, not the automatic inheritance of previous authorization.

Under general transaction authorization principles, the user confirms significant data and the server checks authorization before execution. This must be implemented separately for the store. Specify in the brief which fields affect the validity of approval and when a proposal expires.

Check the cart, not just the catalog price

Final price control is needed wherever a base value combines with discounts, coupons or customer group terms. The approved price list and the actual amount payable may differ under the defined rules. The business therefore needs to determine at which stage to check its constraints and what to include in the calculation.

Drupal Commerce separates the mechanisms for price determination and adjustments. Adjustments can represent promotions, taxes, fees and shipping at order or order item level. This is described in the official Drupal Commerce documentation. It explains the technical mechanisms, but does not provide a ready-made approval policy or a universal margin check for your store.

A hypothetical example: a household goods chain approves a new price for a tool set. The catalog change is correct, but a category promotion and a coupon both apply in the cart. The chain's internal rules do not allow these offers to be combined. The acceptance criterion here is not “the price was imported successfully,” but “for this set, the cart applies only the permitted combination of terms.”

Agree on a response to violations: block publication, refer the item to the responsible person or disallow a particular combination of discounts. Do not leave this to whatever order the modules happen to run in. Likewise, define the behavior for different currencies, sales units and tax settings. Authorized business specialists formulate financial and legal rules; the developer turns them into testable logic.

If the same SKU means different packaging or variants in different systems, sort out identification first. To prepare this layer, see the article on product catalog structure for AI, SEO and marketplaces. For pricing integration, the consequence is what matters: the approved value must reach the correct sales unit.

Make approval part of the operation, not a note

A price list approval workflow should be described through operational states: “received,” “checked,” “awaiting a decision,” “approved,” “being transmitted,” “applied” or “error.” This is a suggested scheme, not mandatory field names. Its purpose is to let the team distinguish between authorization, data transmission and an actual change on the website.

Define a role and a condition for every transition. The initiator prepares the proposal, the responsible person confirms it, and the integration transmits the authorized version. Where necessary, the business assigns preparation and approval to different people. Permissions are checked on the server: a hidden interface button must not be the only barrier to a change through another exchange route.

Before applying the change, recheck that authorization and important input conditions remain valid. New purchasing information may have arrived, a promotion may have ended or the price list itself may have changed between reviewing the record and execution. Specify in the brief which changes stop the operation. Missing data must produce a clear exception, not a silent “everything is fine” decision.

Agree separately on open carts and orders that have already been placed. Does a cart retain the previous price, when is it recalculated, and how does the customer learn about a change? Do not replace a business decision with the platform's default behavior. A new price list for future purchases must not quietly turn into a revision of the history of already accepted orders.

What to do when only some products have been updated

A sent file or a successful response from an API, the software interface for data exchange, does not yet give the full picture. Agree on how to obtain confirmation of applied prices: which items have been accepted, which rejected and which are awaiting processing. For a manager, this is the difference between a completed operation and a batch that still requires action from the team.

The requirements should allow redelivery of the same batch without repeating changes that have already been completed. This requires an operation identifier, version control for the operation and state reconciliation. If the connection drops, the system must first establish the outcome rather than create a new change blindly. An outdated message must not overwrite a more recent approved price list.

Define acceptable behavior for batches: apply each eligible item separately or wait until the entire set is ready. This depends on the business relationship between the products. A bundle and its components may require a coordinated transition; for independent products, a partial result with visible exceptions may be acceptable. Choose the rule before development, not after the first failure.

Plan how to stop the queue and return to previous terms. A price rollback is a new controlled operation: blindly restoring an old file can erase later authorized changes. Retain previous values, check the current version and identify who is responsible for the decision. If the price has already reached advertising or another channel, reconcile that channel's state separately: the website cannot itself confirm the state of another system.

Accept the integration through a rehearsal of a working day

Pricing integration acceptance tests must demonstrate more than a successful update. Ask the implementer to run through the sequence your team will follow in a test environment. Use a prepared set of products and agreed expected results, not real sales with accidentally changed prices.

  1. Create a proposal for a standard product and a variation. Check the SKU, channel, currency and how the change is displayed to the responsible person.
  2. Approve a version, then change a significant field. Make sure the new proposal has not inherited the old authorization.
  3. Try applying the price list without approval and as a user without the necessary permissions. Expect a rejection and a clear event record.
  4. Check the product in the catalog, on its product page and in the cart with active promotions. Compare the total with the approved business rule.
  5. Simulate an interrupted exchange and redelivery. Establish the state of each item and make sure a completed operation is not executed again.
  6. Stop the batch and rehearse restoring a price after another authorized change. Check that newer data has not been overwritten.

Keep sample records, actual states and explanations of deviations in the test report. The store team must be able to find a problematic item and refer it to the responsible person without reading a technical log.

What scope of work to discuss with the web team

Estimating store enhancements starts with a map of the current price flow and the available exchange interfaces. The timeline depends on the quality of product identifiers, the ability to retrieve current discount rules, access to a test environment, the method of confirming results and how quickly exceptions are approved. Unclear responsibility for these rules is just as much a dependency as missing ERP access.

The estimate should show the cost components and work budget: process description, data validation, exchange development, an approval screen, permissions, operation history, tests and team training. Account separately for operations: error monitoring, integration support and external service fees if a service is needed. Compare proposals by this scope, not just by the label “price import.”

GL.ua develops Drupal stores and web systems and integrates them with business systems. This is an appropriate starting point for discussing a controlled flow of prices on the website; defining commercial policy remains your business's responsibility. For the first discussion, prepare a sample price list without confidential data, a list of channels, current discount rules and a situation that currently requires manual intervention.

If the problem is specifically transmitting and applying prices that have already been determined, discuss store development and the necessary integrations with GL.ua. The initial task is to agree on the workflow for a single change and its acceptance criteria. The next price list can then become a controlled operation, rather than another spreadsheet that everyone has to check on their own.

Order a site now!

Just one step to your perfect website

Accessibility menu
Contrast settings
Font size
Letter spacing
Line height
Images
Font
Reset the settings