Update and correction policy
PC specifications are relatively stable; prices, stock, seller details, and lifecycle status are not. GixCore handles those fields differently and makes the limits explicit.
Page refresh behavior
The production catalog uses server-rendered pages with scheduled revalidation. Category hubs can refresh about hourly, while individual part pages can refresh about every ten minutes. These intervals control when GixCore asks its catalog service for a newer record; they do not guarantee that every upstream source changed during that interval.
Prices and availability
When price display is enabled, the product page may show when that price was recorded. Price-dependent value signals can move as the market changes. The retailer page remains the final source for the price, stock, seller, shipping terms, and availability that apply at purchase time.
Specifications and editorial content
Core specifications are updated when a stronger source, a verified correction, or a new model-specific record becomes available. Release dates, discontinuation notes, and editorial summaries may be revised independently of the underlying hardware fields. The sitemap carries each catalog record's latest available update timestamp to help crawlers prioritize changed pages.
Correction priorities
Reports are generally more urgent when they could change a purchasing or compatibility decision. Examples include:
- Incorrect socket, RAM generation, form factor, interface, wattage, or capacity.
- A product page attached to the wrong variant or retailer identifier.
- A broken official source, product image, or purchase link.
- A summary that conflicts with the displayed specifications or cited source.
How to report an issue
Send the page URL, the field or statement in question, and a model-specific source that supports the correction. Reports can be submitted through the site's feedback control or the channels listed on the Questions & Answers page.