Bundles for stores whose orders leave Shopify.

Most bundle apps are sold to the marketing team on conversion. The costs, when the architecture is wrong, land on you: pick lists a warehouse cannot read, order exports finance cannot reconcile, inventory counts that need supervision. Solid Bundles was built from the opposite end, the order backwards: bundles serious operations can trust. Here is exactly what that means at the data level, and how to verify each claim yourself in under an hour.

1. The order shape: original prices, per-line allocation

When a kit sells, the order contains its components as real line items. Each line carries the component's own SKU and its original catalog price, with the bundle discount explicitly allocated per line, plus a reference to the parent kit. A three-item kit at $59 with $9 off looks like this in the order:

Every line still matches your price list, and the discount is explicit instead of baked into a recomputed per-line price. That is the difference between an export your ERP reconciles automatically and one that needs a mapping table and an explanation at month-end. Refunds work at component level: return one item, restock that component.

Verify it: place a test order (Bogus Gateway on a staging store) and read the raw order in Shopify admin or over the Admin API. The 3PL guide shows the exact payload shape.

2. The write surface: none

The app has no write access to your inventory. Bundle availability is computed at read time from live component stock, and expansion happens during checkout through Shopify's native Cart Transform, so components decrement natively, by Shopify itself. There is no sync job, no bundle inventory record, and therefore no failure mode in which the app corrupts a count. Uninstalling leaves products and inventory exactly as they were.

For an IT owner this is the shortest risk review in the category: an app that cannot write your inventory cannot damage it, and cannot fight your ERP connector for the same numbers.

Verify it: read the permission list on the install screen. There is no inventory write scope to grant.

3. Change control: verified nightly, in every market

Bundle correctness decays: catalogs change, currencies move, discounts collide. Solid Bundles ships a verification engine that builds real test carts in every market you sell in and reports what a customer would pay, per line, per currency, against what you configured. It runs on demand before a launch, and it re-runs automatically every night for every store. Nightly is the default cadence; operations customers can have a tighter schedule on request. Drift shows up in a report, not in a customer email or a reconciliation break.

Verify it: install on staging, click Verify, read the report. Then read it again the next morning.

4. Sidekick, scoped and permission-checked

Solid Bundles ships Shopify Sidekick extensions: from the admin assistant your team can search offers, read a bundle's configuration, query buildable sets from live component stock, and pull the latest verification result, all inside Shopify's own permission model. Useful for the person who asks "can we still promise 500 gift sets for the campaign?" without opening another tool.

5. Multi-store organizations

Shopify bills apps per store, and that is how the app installs: per store, staging included, with development and staging stores free. Organizations running several brands or regional stores get one direct contact for all of them, and one conversation about terms. What we do not promise: centralized cross-store bundle administration does not exist yet, in this app or any other in the category. True today is per-store install, an organization-level deal, and a direct line to the founder.

6. Who is behind it, and what it costs

Solid Bundles is built in Berlin by a deliberately small engineering team, and it is in staging evaluation with enterprise retail operations today, selected for exactly what this page describes: the reconcilable order shape and the zero-write inventory model. The size cuts both ways and you should weigh both: no large support organization, and no ticket queue either. Questions are answered by the developers themselves, usually within hours, CET. Custom bundle requirements, staged rollouts and go-live support are handled directly.

The app is $29 per month, flat, at any volume; the price does not scale with your revenue, your orders, or your store count ambitions. Operations engagements beyond the app itself, such as custom bundle builds, migration of large catalogs, staging support and priority arrangements, are scoped directly with the founder: [email protected].

The one-hour evaluation

1. Install on a staging or development store (free) and define one real kit from your catalog.
2. Run verification; read the per-market report.
3. Place a Bogus Gateway test order; pull it through your actual integration path (ERP connector, 3PL portal, or raw Admin API) and hand the result to whoever reconciles orders.
4. Refund one component; watch stock restock.
5. Check the install screen's permission list against your security checklist.

If any step disappoints, you have spent an hour and installed nothing in production. If they all pass, you have already done the integration test that usually takes a sprint.

Technical depth first? Read the 3PL and fulfillment guide and the setup docs. Comparing against the kit-app incumbent? See the Simple Bundles comparison.