The visitor must be able to understand the conditions applicable to his product and his destination before continuing his order. Align Sheet, Basket, Policy Page, and Structured Data. The markup describes the conditions of the company; He doesn't define them for him.
Inventory the actual proposed situations
List destinations served, delivery methods, fees, possible limits and catalog exceptions. Have the information confirmed by the people responsible for the offer and operations. Do not copy a legal or commercial model without verification. This article deals with display consistency: the conditions applicable to your activity must be validated in the appropriate framework.
Show information in the right place
A sheet should explain the elements useful for the decision and refer to a complete accessible policy. The basket must confirm the calculated conditions for the destination and the selected products. Avoid general formulations that suggest a free or universal time frame when exceptions exist. Consistency also counts in messages sent after order.
Separate the approved policy from its technical representation
The first reference source is the company's approved policy, with validations adapted to its activity. The site must then represent it correctly in the contexts concerned. A structured data does not create a commercial condition and does not allow you to choose a deadline, a fee or an exception instead. This article describes a display acceptance test, not the legal rules applicable to each shop.
| Support | Information to check | Example of a discrepancy to be dealt with |
|---|---|---|
| full policy | Validated conditions, destinations and exceptions | An exception is no longer applicable but remains published |
| Product page | Useful conditions for decision for this product | A general formula hides a particular case |
| Basket | calculation corresponding to the composition and destination | The amount differs without explanation |
| Structured data | conditions actually issued for this scope | An old policy remains in the markings |
| Confirmation messages | Information consistent with the validated route | An old message template announces something else |
The Google Documentation MerchantReturnPolicy In particular, distinguishes the general policy and the possibilities of representation related to the offers. Check the supported properties before you code an exception. A property present in a vocabulary does not necessarily mean that it is used in all displays of an engine.
Describe the conditions in the data
Google documents MerchantReturnPolicy to represent return information, as well as the possibility of a general policy or exceptions depending on the case supported. Implement only validated and visible information. Check the current version of the pre-development documentation. Correct structured data does not ensure that Google will display it in a result, and does not correct an ambiguous business page.
Fictional example: a large object
A shop applies fees specific to a bulky product. The policy page describes this exception, but the sheet still displays a general free shipping message. The team corrects the message and the calculation, then tests a demo command on the destinations concerned. It also checks that the catalog flow does not keep the old indication after synchronization.
A set of cases to detect inconsistencies
- Define a standard case with a supported reference and destination. Note the conditions expected from the validated policy.
- Add a product with a real exception. Check that the text and calculation make this exception understandable without waiting for the last step.
- Try an unserved destination and a combination of products with different conditions. The expected behavior must be decided by the company, not improvised during the acceptance test.
- Finally, check the structured data and product messages for these cases. Use demo commands in the intended environment, without unnecessarily triggering payment or shipping.
In a fictional example, a large object does not benefit from the same costs as a small accessory. The sheet announces this difference and the basket applies the validated rule. If the export still displays an old condition, the update process must be examined. Changing only the visible sentence would leave the problem on the other media.
The Deliverable for a Resume Store can be a case table, a list of discrepancies and proofs of correction. Add the manager of the next review, especially when changing carriers or catalogs. The Consistency of flows and product data Complete this acceptance test; the Clarity of sheets for purchase assistants benefits without this guaranteeing a recommendation or an enriched display.
Organise a consistency check
Test a standard case, exception, unserved destination, and a combination of products. Compare the results with the approved rules, without making any unnecessary real purchase. Keep control examples for each change. This work completes the Catalog, price and stock synchronization and helps to limit misunderstandings that then come to support.