Product options app or custom builder?

Start with an app when the workflow is standard.

Text fields, swatches, file uploads, conditional choices, and paid add-ons are available in existing Shopify apps. Compare the actual behavior, not just a feature checklist: how does the price reach the cart, where is the artwork stored, and what does the merchant receive with the order?

Test the setup on your theme and mobile devices. Include subscriptions, setup work, ongoing support, and the consequences of removing the app in your budget.

Consider custom work when the systems need to agree.

In the Direct Laser Source project, supplier catalog data, availability, store-specific margins, quantities, and decoration choices feed an apparel ordering experience. The editor also shows artwork placement and decoration previews. That combined workflow is more specific than adding another product field.

Custom work can still use existing tools. The scope might be theme integration, a pricing service, a supplier connector, or a full builder; it does not have to mean replacing every part of Shopify.

Conditional options need a clear rulebook.

Write down which choices reveal or exclude other choices, what changes the price, and which configurations must be blocked. The CARBON.DEPT and Jalisco wheel flows provide concrete examples of presenting a specialized product with dependent options.

Test a valid configuration, an invalid combination, a changed selection, an unavailable item, and the final handoff. A polished preview alone does not prove that the backend receives the correct order.

Ask these questions before approving a quote.

• Which system is the source of truth for products, stock, and pricing?
• How often does supplier data refresh, and what happens when it is unavailable?
• Does the selected price reach a real cart, a quote request, or another order system?
• Where are uploaded files stored, and how does production receive them?
• Who owns the accounts, source code, and ongoing maintenance responsibilities?
• Which test configurations and mobile flows are included in acceptance?

Define the boundary, then choose the approach.

Use an app when it meets the requirement cleanly. Discuss custom development when the important gap is specific and demonstrable. Both approaches need testing and a clear handoff.

References: an example of an existing product-options app and SanMar integration options. Feature availability and supplier access must be checked for the proposed project.