Satechi's Four-Display Dock: A Practical Shopify Guide to Clearer ChatGPT Product Information

Official manufacturer image, used for product-information teaching; not a WESWOO client project.

Visit the product page for Satechi's Thunderbolt 4 Multimedia Pro Dock and one of its main selling points is immediately apparent: support for up to four displays. But expand the Compatibility section and the picture becomes more specific. Base M1 and M2 MacBooks are limited to one external display, while base M3 MacBooks need to operate in clamshell mode to support two external displays.

The dock itself hasn't changed. What changes is whether it can deliver the experience a particular buyer expects, based on the computer they're using.

That's an important distinction for merchants. Someone asking ChatGPT to recommend a dock isn't necessarily interested in its documented maximum display capability. They want to know whether it will work with their own setup. A product description that only highlights the headline specification doesn't answer that question.

This guide uses a real Satechi product to walk through a practical Shopify workflow: organize product information, check what Shopify Catalog receives, distinguish purchasable variants from compatibility requirements, and test whether the selected version remains consistent across the storefront.

The information comes from Satechi's public product page and support documentation. The Shopify Partner Directory also lists a Shopify website project for the brand. The admin workflows discussed below are implementation recommendations, not descriptions of Satechi's private fields, apps, or theme code. We have not verified the brand's current ChatGPT listings. Project reference.

1. Start with the product itself: plug options don't change display capability

On the Satechi product page, the purchase option is labeled Plug. During our visit, it offered US, EU, and UK versions, with the following published SKUs:

Purchase option	Published SKU	What the choice identifies
US	ST-DT4PMM-US	US plug version
EU	ST-DT4PMM-EU	EU plug version
UK	ST-DT4PMM-UK	UK plug version

These aren't different performance tiers, such as a single-display version and a four-display version. Selecting another plug changes the physical power-plug version, not the display capabilities of the host computer.

Power specifications need the same careful distinction. Satechi lists an approximately 0.8 m Thunderbolt 4 cable and a 135W power supply as included items. Host PD charging, however, is limited to 96W. The 135W rating describes the supplied power adapter; it does not mean the laptop receives 135W of charging power. Package and power details.

For the merchant, these details belong in three different places:

• Plug options belong in the purchasable variants.
• Display restrictions belong in compatibility information.
• Included accessories belong in the package contents.

Keeping those categories separate makes the product easier to maintain and reduces the chance of a buyer misunderstanding what a variant actually changes.

2. Describe capabilities together with the conditions behind them

A useful first step is to review the product record for statements that describe an outcome without explaining when it applies.

This dock is a good example. Base M1 and M2 MacBooks are limited to one external display. Base M3 MacBook Air and MacBook Pro models require clamshell mode to support two external displays. Satechi also states that this model neither requires nor supports DisplayLink or SiliconMotion software.

One detail matters here: restrictions documented for base chips should not be generalized to every Pro- or Max-chip configuration. Compatibility needs to be tied to the specific host models and conditions in the official documentation. Compatibility; software requirements.

A practical content review can use the following table:

Information to examine	What the record needs	Maintenance location
Maximum display capability	Supported host, operating conditions, and limits	Description and compatibility content
Power figures	Included supply rating versus host charging limit	Package list and power specifications
US, EU, UK	A clear plug option, not a performance tier	Variant option name and values
Software	Requirements and exclusions for this exact model	Product explanation and FAQ

In Shopify, open Products → the product. Review the description, then inspect the relevant Variants row for its options, SKU, price, inventory, and media.

Shopify is rolling out a redesigned product editing experience, so some stores may manage variants directly on the same page rather than through separate detail screens. Editing variants.

Have the content owner identify what each statement applies to, and the product specialist check the technical conditions. The developer can then decide how to display the approved information.

Ideally, a developer should be working from a verified compatibility matrix, not trying to reconstruct one from a headline that says the dock supports four displays.

Give shared specifications a clear place to live

When the same compatibility information appears in the product description, FAQ, and theme components, each copy becomes another place that someone has to remember to update.

For a custom storefront, it's better to decide where approved product information belongs before adding more display components.

A suggested Shopify workflow:

1. Go to Settings → Metafields and metaobjects and check whether an existing standard product definition already covers the information. If it doesn't, create suitable multi-line text definitions for compatibility restrictions and package contents. These are suggested fields for this workflow, not a disclosure of Satechi's actual admin structure.
2. Open Products → the product → Metafields, enter the verified conditions and included items, and save. Keep prices and inventory in their native Shopify records rather than duplicating them in text fields.
3. In the theme editor, open the product template and connect supported text or collapsible blocks to the relevant dynamic sources. Preview another product to make sure its own information appears correctly, then save.

The sequence matters: create the definition, enter its value, and connect it to the storefront.

Creating a metafield definition doesn't automatically display anything on the product page. Likewise, displaying a metafield in the theme doesn't automatically make it the description source used by Shopify Catalog.

Shopify documents each part separately: Definitions, values, and theme connections.

3. Check which description Shopify Catalog actually receives

A custom product page might display detailed compatibility information from a metafield, while the original Description field still contains an older introduction.

In that situation, fixing the visible page alone doesn't resolve the separate data source that Catalog may be using.

Open Sales channels → Agentic → Shopify Catalog in Sources → Review product data mapping. Under Product fields, check the source currently mapped to the description.

If the approved description lives somewhere else, select the appropriate source, preview the product, and save the change. Shopify notes that an empty mapped source falls back to the default field, so it's important to check field coverage across products rather than relying on one fully completed example. Catalog mapping.

The following checks help identify where a correction is actually needed:

Check	What to look for in the data preview	Corrective action
Description	Host conditions alongside display claims	Fix the actual exported source, not just the theme component
Purchase option	Plug still means plug	Correct the product option if its meaning is unclear
Price	Current selling price versus reference price	Check variant pricing and List price separately
Package and power	Supply rating separated from host PD limit	Correct the source and align the page with it

One pricing detail is easy to overlook. Catalog's List price can use either Price or an eligible Compare-at price. That setting doesn't determine which merchant's price ChatGPT displays in its initial shopping results.

OpenAI explains that initial prices typically come from the first listed merchant, may not be the lowest available, and can take time to update. ChatGPT pricing explanation.

If an exported description is missing a compatibility restriction, correct the source that feeds the export.

If the exported data looks right but an external AI summary leaves out the restriction, preserve the original query, complete result, landing link, and timestamp before reporting the discrepancy.

These are two different problems and shouldn't be treated as the same synchronization issue.

4. Group actual product versions, not an entire category

It's reasonable to treat different plug configurations of the same dock as product options. It's not reasonable to group every related docking product into the same model.

For example, the Thunderbolt 5 CubeDock and Thunderbolt 4 Slim Hub Pro appear in Satechi's related-products area. They are separate products. Sharing the same general dock category doesn't make them plug variants of the Thunderbolt 4 Multimedia Pro Dock.

When reviewing your own catalog, start by checking the product relationships under Products. Only consider Custom variant grouping when versions of the same product are maintained as separate product records and grouping them for the channel makes sense.

Shopify Catalog supports grouping by title delimiter, product metafield, or tag prefix.

There is one important consequence: enabling custom grouping overrides Catalog's use of Combined Listings settings. Before saving, inspect Products in group to make sure the right records are included.

If a need review result appears, investigate whether there are duplicate option combinations. Don't solve the problem by inventing an arbitrary model suffix that doesn't reflect a real product distinction. Grouping and review results.

The aim is a clear purchasing decision. Buyers shouldn't be led to believe that choosing a different plug gives them capabilities that belong to another device.

5. Put compatibility information where buyers make their decision

Satechi already provides expandable sections for technical specifications, compatibility, and important information. That makes the details available, but merchants should also consider whether the most important restrictions are visible when someone is ready to purchase.

Observed during this visit: base M1/M2 and M3 restrictions in Compatibility, with Plug: US in the purchase bar. US$349.99 and Sold Out describe this session only.

The following is a design recommendation, not a feature we claim Satechi has implemented.

Consider adding a short host-compatibility check near the purchase area. It could identify the buyer's chip, ask how many external displays they need, and check for clamshell use when the base M3 condition applies.

Confirmed condition	Expected page response
Base M1/M2 MacBook, requesting two independent external displays	Explain the product's single-external-display restriction
Base M3 MacBook, requesting two external displays	Ask about clamshell operation before presenting a positive result
Only “MacBook Pro” is known	Ask for the chip from About This Mac; do not infer it
The requirement relies on DisplayLink	Show that this model does not support that software solution

The development team should work from a verified rule set. If a model or configuration hasn't been covered, its compatibility should remain unconfirmed rather than being presented as a definite yes.

The compatibility interaction and the Plug selector serve different purposes. One checks whether the product suits the buyer's intended setup; the other identifies which physical version they're purchasing.

For a small number of fixed notices, existing theme blocks may be enough. If the guidance needs to change according to several inputs, a custom selector may be more appropriate.

During acceptance testing, check how the explanation changes with the confirmed inputs. Simply confirming that a new AI button appears isn't enough.

6. Make sure the selected version survives when the link is shared

During this session, opening variant=40223722471512 selected the EU version. After clicking US, the main image and Plug text changed to US, but the address retained the original parameter.

This is a single-session observation, not a conclusion about every device, region, or browser.

It does, however, point to a useful storefront test: after changing a variant and copying the address, does reopening that address preserve the version the buyer selected?

Shopify documents variant deep links using actual variant IDs and explains that variant-specific product information should follow the selected variant. Theme variant support.

A practical test sequence:

1. Open a real deep link for EU. Check the selected option, image, price, and purchase state.
2. Switch to US, copy the current address, and open it in another tab. If it still selects EU, document the mismatch between the selected state and the shared link for the theme developer to investigate.
3. If inventory and test authorization allow it, add one unit to the cart. Check the model, plug, quantity, and amount shown in the cart. This verifies the actual add-to-cart result; a highlighted option by itself doesn't.

The page displayed Sold Out during this visit, so we didn't test the cart or checkout.

For your own preview theme and authorized test conditions, cover available, unavailable, and return-to-page states. An unavailable version should never silently become another in-stock version in the cart.

7. Check the package contents before recommending accessories

The actual Related Products area included checkboxes for other expansion devices. But a related product isn't necessarily something a buyer needs in order to use the selected dock.

This is particularly relevant here because the dock already includes a power supply and host cable. Before recommending additional purchases, check whether they duplicate something in the package.

A longer cable, for example, introduces its own length and protocol requirements. If the buyer needs a different display configuration, recommending another dock as a substitute may make more sense than suggesting two docks as a presumed bundle.

To manage recommendations in Shopify, open Apps → Search & Discovery → Product recommendations → Add recommendations.

Select the product, assign additional-use items to Complementary products, and use Related products for substitutes. Save the changes, then add a supported recommendation block to the product template.

Complementary products also need to be in stock and have Active status to appear. Recommendation configuration.

These are product-level recommendations. Selecting items conditionally according to the buyer's host computer, package contents, and chosen variant requires defined business rules and appropriate storefront logic.

A recommendation should never be treated as proof of compatibility.

Keep the purpose of each part clear:

• Plug changes the purchasable version.
• Compatibility guidance checks the intended use.
• Alternative models address different requirements.

8. Keep evidence that shows exactly what changed

After updating the product information, open Sales channels → Agentic, run a relevant search, and expand Listing insights.

Review the available signals for description, images, reviews, variants/options, and policies. The preview represents Catalog search, while an external AI channel may rank results differently. Search preview and listing signals.

For each change, keep the original query, source information, preview, timestamp, and a record of what was updated.

A quality indicator alone doesn't explain what was wrong or how it was fixed.

The following two prompts can help audit an external answer about this specific product:

Using Satechi's official documentation, explain whether the Thunderbolt 4 Multimedia Pro Dock can provide two independent external displays for a base M2 MacBook Air. Cite the restriction and source rather than substituting the maximum four-display claim.

What do the dock's 135W supply and 96W PD figures each refer to? Does the package already include power and a host cable? Distinguish included items from purchases that are necessary separately.

The first prompt checks whether host-specific display conditions are preserved. The second checks whether power specifications and package contents are being described correctly.

These are audit prompts, not test results we obtained or evidence of a completed recommendation experiment.

A useful evidence record can look like this:

Evidence to retain	What it establishes
Description source and product preview	Restrictions are present in exported information
Product records, package list, and page	Model, plug, and power meanings are consistent
Before/after links and reopened selection	The intended version survives the link
Actual cart lines, where testing was performed	The added version matches the choice
Query and complete AI answer	Whether that answer preserved the critical conditions

Shopify also documents automatic /agents.md, /llms.txt, and /llms-full.txt discovery endpoints.

These files provide store-discovery information, but they don't replace Catalog product data. For the issue discussed in this guide, checking the product description, variants, and field mapping is a more direct starting point than buying a separate file-generation tool. Discovery files versus product information.

From WESWOO's perspective on custom store design and development, this is part of delivering a maintainable storefront: product information that can be updated, options buyers can understand, usage restrictions that are easy to find, and an order that still reflects the version they selected.

For this dock, the final checks come down to three straightforward questions:

• Can the buyer's computer use the dock as intended?
• Which plug version are they actually purchasing?
• Does the cart still contain that same selected version?

Sources and storefront observations checked on November 4, 2026. No access to the brand's admin, hardware test, checkout test, or verification of its actual ChatGPT recommendations was performed.