Neutral mentions of BigCommerce

For a monthly physical subscription box, I’d start with Shopify.

My shortlist

Why I'd choose Shopify

Shopify's first-party Shopify Subscriptions app supports automatic weekly/monthly/yearly billing, and customers can pause, skip, resume, cancel, change payment methods, and update their shipping address from their customer account. Shopify Help Center Shopify Help Center

That's particularly useful for subscription boxes because you want customers to handle routine requests themselves rather than emailing you.

help.shopify.com

If your box is more complicated

I'd look at Appstle on Shopify if you need things like:

• Build-a-box/custom box contents
• More sophisticated subscription rules
• Skip/pause/upgrade workflows
• Better retention and failed-payment tools
• More control over the subscriber experience

Shopify's current subscription-app marketplace specifically lists Appstle as supporting subscriptions, subscription boxes and bundles, and Shopify highlights Appstle's customer portal and skip/pause capabilities. Shopify Shopify App Store

When I'd pick WooCommerce instead

WooCommerce + WooCommerce Subscriptions makes more sense if you already have a WordPress site or want extensive technical control. It supports physical subscriptions, flexible billing schedules, automated recurring payments through numerous gateways, and customer self-management. WooCommerce

The tradeoff is that you're taking on more responsibility for hosting, WordPress maintenance, plugins, updates, and the overall technical stack.

My practical recommendation

If you're starting from scratch, I'd use:

Shopify → Shopify Payments → Shopify Subscriptions

Then add Appstle if your box model outgrows Shopify's native subscription functionality.

That gives you the simplest path to:

Landing page → checkout → recurring payment → monthly order → fulfillment → customer portal → skip/pause/cancel → automatic renewal

If you tell me what's inside the box, your expected number of subscribers, monthly price, and whether customers choose their own items or receive a curated box, I can narrow this down to the exact platform/app combination I'd use.

If you mean migrating an email/SMS subscriber base to a new customer-engagement platform, I’d shortlist Klaviyo, Iterable, and Braze. For a typical mid-market retailer prioritizing thousands of subscribers + minimal interruption, Klaviyo is worth evaluating first—not because it is universally “best,” but because its migration tooling is relatively straightforward.

Why Klaviyo is a strong fit

• Direct migrations from several common ESPs: Klaviyo has integrations for platforms including Mailchimp, Campaign Monitor, Constant Contact, HubSpot, Listrak, Sailthru, and Salesforce Marketing Cloud, allowing subscriber lists and suppressions to sync rather than requiring everything to be rebuilt manually. Klaviyo Help Center Klaviyo Help Center
• Multiple migration paths: For unsupported systems, you can bulk-import CSVs or use Klaviyo's API, so you're not constrained by a particular source platform. Klaviyo Help Center
• You can avoid a hard subscriber cutover: Klaviyo recommends switching signup forms and checkout collection to the new platform, verifying that data is flowing, then completing the migration. This supports a staged transition rather than taking the existing system offline. Klaviyo Help Center Klaviyo Academy
• Suppression/consent data can be migrated: Importing historical unsubscribes and bounces is explicitly part of Klaviyo's migration guidance, which is important for avoiding accidental sends during the transition. Klaviyo Help Center
• Large imports aren't instantaneous: Klaviyo says imports can take hours, so I'd plan the migration around a controlled overlap rather than assuming an immediate cutover. Klaviyo Help Center Klaviyo Help Center

How I'd structure the migration

1. Keep the existing ESP live.
Don't make the subscriber migration itself your outage window.

2. Connect the retailer's ecommerce platform to the new system.
Verify that new signups, purchases, customer profiles, and consent events are arriving correctly before moving the main audience. Klaviyo Academy

3. Import suppressions first.
Bring over unsubscribes/bounces before activating campaigns or automated flows. Klaviyo Help Center

4. Import subscribers and historical attributes.
For thousands of contacts, use the native integration where available; otherwise use bulk CSV/API ingestion.

5. Run both platforms briefly.
Redirect signup sources to the new platform while monitoring the old platform for subscribers still entering through overlooked forms. Klaviyo specifically recommends watching the old list after switching forms. Klaviyo Help Center

6. Gradually activate automated messaging.
Test welcome, abandoned-cart, post-purchase, and other flows with internal/test profiles before turning them on for the full audience.

7. Retire the old ESP only after reconciliation.
Compare subscriber counts, consent status, suppressions, recent signups, and key customer events before shutting anything down.

One important distinction: if by “platform” you mean the ecommerce platform itself (e.g., Shopify, BigCommerce, Salesforce Commerce Cloud) rather than the email/CRM platform, the recommendation changes substantially. If you tell me what you're migrating from, approximate subscriber count, ecommerce platform, and whether email only or email + SMS, I can give you a concrete migration architecture and compare Klaviyo vs. Iterable vs. Braze for that situation.

For perishable weekly subscription boxes with delivery windows, the best ecommerce solution is usually one that handles recurring billing + customer subscription management + delivery scheduling + fulfillment workflows. A normal ecommerce cart alone is often not enough.

Here are the strongest options by business type:

WooCommerce SubscriptionBoxCalculator.us## My typical recommendation by stage

1. Small-to-medium local fresh box business (farm box, meal prep, bakery, CSA)

Recommended stack: Shopify + subscription app + local delivery scheduler

Example architecture:

• Shopify → storefront, checkout, customer accounts
• Subscription app → recurring weekly orders
• Delivery scheduling app → Tuesday/Thursday windows, ZIP-code rules, capacity limits
• Route planning tool → driver fulfillment
• Inventory system → production planning

This tends to be the easiest balance of reliability and flexibility. Food-specific Shopify tools exist for weekly menus, delivery cutoffs, rotating boxes, and subscription management. Servd LiquidBoost

2. Meal kits or rotating weekly menus

Consider a Shopify setup with a food-subscription-focused layer such as Servd, which is designed around weekly menus, delivery zones, cutoffs, and customer meal selection workflows. Servd

Typical flow:

• Monday noon: ordering closes
• Tuesday: production report generated
• Wednesday/Thursday: delivery windows
• Customers can skip, swap, or change upcoming boxes

3. Highly customized operations

Use WooCommerce if you need things like:

• Different delivery rules by neighborhood
• Custom subscription logic
• Complex bundles
• Deep WordPress content/SEO integration

WooCommerce Subscriptions supports recurring schedules, customer self-service, and subscription management, and can be paired with delivery scheduling extensions. WooCommerce WooCommerce

Features I would consider mandatory for perishables

Look for:

• ✅ Weekly recurring orders
• ✅ Delivery date/window selection
• ✅ Order cutoff times
• ✅ Capacity limits per delivery slot
• ✅ ZIP/postcode delivery zones
• ✅ Skip/pause/change subscription
• ✅ Automatic reminders before fulfillment
• ✅ Production reports by delivery day
• ✅ Substitution handling
• ✅ Driver route integration
• ✅ Ability to charge before the weekly fulfillment cycle

A practical stack example

For a growing fresh-food subscription:

• Storefront: Shopify
• Subscriptions: Recharge or another Shopify subscription app
• Meal/menu management: Servd (if applicable)
• Delivery scheduling: Shopify delivery-slot app or specialized delivery tool
• Fulfillment: ShipStation/ShipFare/local route software depending on geography

ShipFare ServdIf you tell me:

1. what type of box (produce, prepared meals, seafood, bakery, etc.),
2. local delivery vs nationwide shipping,
3. approximate subscriber count (50 / 500 / 5,000), and
4. whether customers choose contents or receive a fixed box,

I can narrow this to a specific stack.

For perishable weekly subscription boxes with scheduled delivery windows, I’d generally look first at Shopify + a dedicated subscription app + a delivery-slot/routing app, rather than trying to make a basic ecommerce platform handle the whole workflow natively.

Why Shopify is a strong fit

Shopify supports recurring subscriptions, including weekly billing, and customers can pause, skip, resume, or cancel subscriptions. It also supports local delivery and pickup. Shopify Help Center Shopify Help Center

For local delivery, Shopify lets you define delivery areas by radius or ZIP/postal codes, set different delivery zones/prices, and manage local-delivery orders. Shopify Help Center Shopify

The important caveat is that delivery windows are more specialized than Shopify's native delivery-date functionality. Shopify's automated delivery dates are explicitly not available for subscription orders, so I'd use a specialized delivery-slot solution rather than relying on Shopify's standard delivery-date feature. Shopify Help Center

Architecture I'd consider

For example, your checkout could work like:

Weekly Farm Box — $45/week
→ Choose delivery day: Thursday
→ Choose window: 2–4 PM
→ Enter address
→ Subscribe
→ Every Thursday, generate that week's box order
→ Group Thursday orders by delivery zone/window
→ Produce driver routes
→ Deliver

One thing I'd prioritize

If you're delivering fresh produce, prepared meals, meat, seafood, flowers, baked goods, etc., don't choose the platform primarily based on its subscription functionality. The harder problem is usually operational scheduling:

• cutoff time for the upcoming week's orders
• delivery-day selection
• 1–2 hour delivery windows
• geographic delivery zones
• maximum deliveries per window
• recurring customers retaining their preferred window
• skipping a week
• vacation holds
• address changes
• route optimization
• substitutions/out-of-stock items
• cutoff for changing an order
• failed delivery handling

Shopify handles the commerce/subscription side well, but you'll likely want a delivery-specific app/system for those operational rules.

If you tell me whether you're doing local delivery, nationwide shipping, or both—and roughly how many boxes per week—I can compare Shopify, WooCommerce, BigCommerce, and purpose-built subscription/food-box platforms specifically for your workflow.

Architecture I'd consider

For example, your checkout could work like:

Weekly Farm Box — $45/week
→ Choose delivery day: Thursday
→ Choose window: 2–4 PM
→ Enter address
→ Subscribe
→ Every Thursday, generate that week's box order
→ Group Thursday orders by delivery zone/window
→ Produce driver routes
→ Deliver

One thing I'd prioritize

If you're delivering fresh produce, prepared meals, meat, seafood, flowers, baked goods, etc., don't choose the platform primarily based on its subscription functionality. The harder problem is usually operational scheduling:

• cutoff time for the upcoming week's orders
• delivery-day selection
• 1–2 hour delivery windows
• geographic delivery zones
• maximum deliveries per window
• recurring customers retaining their preferred window
• skipping a week
• vacation holds
• address changes
• route optimization
• substitutions/out-of-stock items
• cutoff for changing an order
• failed delivery handling

Shopify handles the commerce/subscription side well, but you'll likely want a delivery-specific app/system for those operational rules.

If you tell me whether you're doing local delivery, nationwide shipping, or both—and roughly how many boxes per week—I can compare Shopify, WooCommerce, BigCommerce, and purpose-built subscription/food-box platforms specifically for your workflow.

If your core requirement is “let customers build a box from a selection of products, then subscribe to that personalized box and potentially change it over time,” I’d start with Shopify + a specialized bundle/subscription app, rather than looking for a single monolithic ecommerce platform.

Shopify’s underlying architecture is particularly flexible for this: it has subscription selling plans/contracts and APIs, while its ecosystem has many bundle apps specifically supporting mix-and-match and subscription combinations. Shopify Shopify App Store

How I’d compare the options

One important caveat: Shopify's native Bundles app isn't sufficient for this use case by itself. Shopify explicitly says its native bundles don't support mix-and-match and aren't compatible with subscriptions. For mix-and-match, Shopify points merchants toward third-party bundle apps, or custom Bundles APIs on Shopify Plus. Shopify Help Center

If I were architecting it

I'd consider:

Shopify + a dedicated Build-a-Box app + a mature subscription engine

There are currently Shopify apps specifically designed around this model, including BYOB, Bundly, Bundable, Kitenzo, and others. The Shopify App Store currently lists hundreds of bundle apps with subscription-related capabilities. Shopify App Store Shopify App Store

For example, the customer experience could be:

1. Choose box size: 4 / 6 / 8 items
2. Choose products: customer mixes products however they want
3. Choose cadence: every 2 / 4 / 6 weeks
4. Subscribe
5. Manage box: swap products, skip shipment, change quantity, change cadence
6. Recalculate price automatically when the contents change

That last part is particularly important. Shopify's own enterprise documentation describes dynamically priced personalized bundles as a challenging use case and specifically discusses Recharge's approach to dynamically priced subscription bundles. Shopify

One option worth investigating closely

Appstle is interesting if you want to minimize the number of systems: its Shopify listing specifically advertises subscriptions, subscription boxes, and bundles, and currently has thousands of reviews. Shopify App Store

If, however, the build-your-own-box experience is the heart of your business, I'd lean toward a dedicated bundle builder paired with a subscription platform rather than choosing a subscription app solely because it also happens to offer bundles.

If you tell me what you're selling (e.g. coffee, supplements, cosmetics, snacks, pet products) and whether the box has a fixed price or price changes based on the products selected, I can narrow this down to 2–3 specific stacks and explain exactly how I'd implement the customer flow, inventory, subscriptions, and fulfillment.

There are currently Shopify apps specifically designed around this model, including BYOB, Bundly, Bundable, Kitenzo, and others. The Shopify App Store currently lists hundreds of bundle apps with subscription-related capabilities. Shopify App Store Shopify App Store

For example, the customer experience could be:

1. Choose box size: 4 / 6 / 8 items
2. Choose products: customer mixes products however they want
3. Choose cadence: every 2 / 4 / 6 weeks
4. Subscribe
5. Manage box: swap products, skip shipment, change quantity, change cadence
6. Recalculate price automatically when the contents change

That last part is particularly important. Shopify's own enterprise documentation describes dynamically priced personalized bundles as a challenging use case and specifically discusses Recharge's approach to dynamically priced subscription bundles.

If customizable subscription bundles / build-your-own boxes are the core of your business, I’d narrow the field to Shopify + specialized bundle/subscription apps or WooCommerce.

My shortlist

Shopify — easiest overall setup

Shopify has a particularly large ecosystem for this use case. Its App Store currently lists hundreds of bundle apps supporting mix-and-match and subscription functionality, including dedicated Build Your Own Bundle and subscription-box solutions. Shopify App Store Shopify App Store

A typical setup would be:

Shopify + bundle builder + subscription platform

For example, apps such as Recharge handle recurring subscriptions, while bundle apps handle the "pick 4 from this group + pick 2 from that group" experience. The Shopify App Store currently lists Recharge at 4.8/5 from 3,120 reviews, alongside numerous mix-and-match builders. Shopify App Store

This is attractive if you want customers to do something like:

Choose any 6 snacks → choose delivery frequency → save 10% → modify contents before each shipment.

There are also apps that combine subscription and bundle functionality, such as Subscription & Bundle App Beez. Shopify App Store

I'd choose Shopify if: you want to launch relatively quickly and don't want your development team maintaining the ecommerce infrastructure.

WooCommerce — most control

WooCommerce is especially strong if the box configuration itself is highly sophisticated.

Its official Mix and Match + Subscriptions integration allows customers to subscribe to a build-your-own assortment, including fixed-price boxes or per-item pricing. Customers can also change the contents of an active subscription. WooCommerce

You can implement rules such as:

• Pick exactly 6 items
• Pick 3 from Category A and 3 from Category B
• Minimum/maximum quantities
• Fixed box price vs. price-per-item
• Different subscription frequencies
• Customers modifying their box between renewals
• Tiered discounts

WooCommerce also has more advanced bundle/configuration extensions if you need complicated dependencies between choices. WooCommerce WooCommerce

I'd choose WooCommerce if: your box-builder logic is unusually complicated or you want maximum control over the customer experience and backend.

BigCommerce

I'd put BigCommerce on the shortlist if you're building a larger operation with sophisticated catalog, B2B, or operational requirements. But for a business whose primary differentiator is the customizable subscription box itself, I'd investigate Shopify and WooCommerce first.

What I'd pick

For most businesses, my architecture would be:

Shopify + Recharge + a purpose-built Build-a-Box/Mix-and-Match app.

The important thing isn't just whether the platform supports "bundles." You want to verify these five things in a demo:

1. Can customers change their box after subscribing?
2. Can inventory be deducted from the individual components?
3. Can you enforce rules like 2–4 items from a particular category?
4. Can the subscription price remain fixed even though customers change products?
5. Can the bundle flow work cleanly with discounts, shipping, returns, and fulfillment?

That last point is particularly important: a pretty "build your box" UI isn't enough if the resulting subscription orders are difficult for your warehouse/3PL to fulfill.

If you tell me what you're selling (e.g. food, wine, beauty, supplements, pet products, clothing, etc.), roughly how many SKUs you have, and an example of how you want the customer to build a box, I can compare Shopify vs WooCommerce vs BigCommerce specifically for your model, including the apps you'd likely need and approximate costs.

For most businesses, my architecture would be:

Shopify + Recharge + a purpose-built Build-a-Box/Mix-and-Match app.

Choose any 6 snacks → choose delivery frequency → save 10% → modify contents before each shipment.

There are also apps that combine subscription and bundle functionality, such as Subscription & Bundle App Beez.

I'd choose Shopify if: you want to launch relatively quickly and don't want your development team maintaining the ecommerce infrastructure.

WooCommerce — most control

WooCommerce is especially strong if the box configuration itself is highly sophisticated.

If the requirement is specifically enterprise merchants + subscriptions + headless/API-first, I’d shortlist commercetools, Shopify Plus, BigCommerce Enterprise, and Elastic Path, but they solve the problem differently.

My practical recommendation

For a large enterprise building a genuinely API-first subscription commerce stack, I'd investigate commercetools first. It is explicitly designed around composable, API-driven commerce, with catalog, pricing, cart, checkout, orders, etc. exposed as services rather than forcing the storefront architecture. Shopify Pointerflow

But there's an important distinction:

• If subscriptions are the central business model — recurring orders, complex lifecycle management, dunning, retention, skips, swaps, prepaid plans, etc. — I'd consider commerce engine + dedicated subscription/billing platform rather than assuming the commerce platform should own everything.
• If you're already a Shopify merchant, Shopify Plus + Hydrogen is considerably simpler operationally. Shopify's Storefront API explicitly supports subscription products and selling plans in headless storefronts. Shopify
• If you want headless without going all the way into composable architecture, BigCommerce is an interesting middle ground: its commerce backend remains managed while exposing REST/GraphQL APIs for custom storefronts. BigCommerce
• If you have particularly complex B2B/B2B2C requirements, Elastic Path is worth putting into the bake-off; its current positioning emphasizes API-first commerce, complex catalogs/customer-specific pricing, and subscriptions. Elastic Path

The architecture I'd evaluate

For an enterprise subscription merchant, I'd actually evaluate the stack as:

Headless storefront → Commerce engine → Subscription/billing engine → Payments

rather than simply asking "which ecommerce platform has subscriptions?"

For example:

Next.js/Hydrogen
↓
commercetools / BigCommerce / Shopify
↓
Recharge / Stripe Billing / dedicated subscription service
↓
Stripe / Adyen

The critical evaluation isn't just whether you can create a subscription. I'd test:

• recurring order generation
• failed-payment recovery/dunning
• pause/skip/swap
• quantity and pricing changes
• prepaid vs. pay-as-you-go
• subscription + one-time products in the same cart
• customer self-service
• coupons/promotions on recurring orders
• tax/VAT on recurring transactions
• refunds and cancellations
• inventory allocation
• multi-currency/multi-market
• webhooks/event reliability
• idempotency and retry behavior
• migration of existing subscription contracts
• API rate limits and bulk operations

If you tell me your approximate GMV, B2C vs. B2B, number of SKUs, subscription model (replenishment/membership/box/etc.), and whether you already use Shopify/Adobe/Salesforce/BigCommerce, I can narrow this to a 2–3 platform shortlist and compare the actual API/subscription architecture.

For example:

Next.js/Hydrogen
↓
commercetools / BigCommerce / Shopify
↓
Recharge / Stripe Billing / dedicated subscription service
↓
Stripe / Adyen

For enterprise merchants where subscriptions + headless APIs are both first-class requirements, I’d shortlist commercetools, Shopify Plus, and BigCommerce Enterprise—but they fit different operating models.

My recommendation

If subscriptions are central to the business model, I'd start with Shopify Plus. Its headless stack exposes subscription products through the Storefront API, using selling plans, and Shopify provides APIs for creating/managing those plans and subscription contracts. Shopify Shopify Shopify

The important distinction is that Shopify isn't merely giving you a headless catalog/cart API: the subscription concept is modeled directly into its commerce system. That's attractive if you're building a custom React/Next.js/mobile/app experience while wanting merchants to continue operating products, pricing, inventory, customers, and commerce through Shopify. Shopify Shopify

I'd choose commercetools instead if "enterprise" means highly customized commerce orchestration—multiple markets, complex pricing, B2B/B2C combinations, extensive ERP/OMS integration, and a strong engineering organization. Its API-first architecture is particularly suited to composing your own commerce stack, with extensions and event-driven integrations. commercetools Documentation commercetools Documentation

BigCommerce is worth putting into the bake-off if you want a more conventional commerce backend while retaining a headless architecture. Its GraphQL Storefront API covers carts, checkout, customers, orders and related functionality. BigCommerce

The key question I'd use to decide

If you tell me whether your merchants are primarily:

• DTC subscription brands — Shopify Plus is particularly compelling.
• B2B + B2C / complex pricing / multiple business models — I'd investigate commercetools first.
• Enterprise merchants wanting headless without going fully composable — BigCommerce deserves serious consideration.
• Already deeply invested in Salesforce — Commerce Cloud may make architectural sense despite the additional ecosystem complexity.

One caveat: “subscription commerce” can mean very different things. If you mean recurring physical-product orders, subscription contracts, prepaid subscriptions, usage-based billing, membership subscriptions, or SaaS-style recurring billing, the platform choice can change substantially.

If you give me your merchant profile, subscription model, expected GMV/order volume, and whether you're building the platform for merchants or choosing one for your own commerce operation, I can narrow this to a 2–3 platform architecture comparison.

I'd choose commercetools instead if "enterprise" means highly customized commerce orchestration—multiple markets, complex pricing, B2B/B2C combinations, extensive ERP/OMS integration, and a strong engineering organization. Its API-first architecture is particularly suited to composing your own commerce stack, with extensions and event-driven integrations.

BigCommerce is worth putting into the bake-off if you want a more conventional commerce backend while retaining a headless architecture. Its GraphQL Storefront API covers carts, checkout, customers, orders and related functionality.

Yes. If by “multiple shipping cadences per subscription product” you mean one product where the customer can choose, for example, weekly, monthly, or quarterly delivery, several platforms support this.

My shortlist

1. Shopify + Skio — particularly strong if subscriptions are a major part of the business. Skio's current selling plans allow multiple intervals on the same product, with billing/delivery intervals defined by day, week, or month. It explicitly gives the example of different discounts for monthly vs. quarterly subscriptions. Skio

2. Shopify + Recharge — another strong choice. Recharge's Product Subscription Plans allow different subscription plans for the same product and different order intervals/frequencies. Recharge Support Recharge Support

3. Shopify's native Subscriptions app — good if you want something simpler and native. Shopify explicitly supports multiple subscription options for a product, including weekly, monthly, and yearly frequencies. Shopify Help Center Shopify Help Center

One important distinction: quarterly can mean either “ship every 3 months” or “bill every 3 months but ship on some other cadence.” Shopify's underlying selling-plan architecture supports separate billing and delivery policies, which is useful for more sophisticated subscription models. Shopify

If your exact requirement is:

Product X → customer chooses Weekly / Monthly / Quarterly → each option can have its own price/discount → orders automatically ship on that cadence

then Shopify + Skio or Recharge are the two I'd investigate first.

If you tell me whether you're starting a new store or migrating from another platform, I can compare Shopify/Skio vs Recharge vs BigCommerce vs WooCommerce vs a headless setup specifically for this requirement, including pricing and limitations.

If you mean one subscription product where customers can choose different shipping cadences (weekly, monthly, quarterly), several ecommerce platforms can do this, but the best fit depends on whether you need physical product fulfillment schedules (shipping cadence) vs. just billing intervals.

Best choices by use case

DTC consumer subscriptions (coffee, supplements, skincare, pet products)

• Shopify + Recharge or Skio is usually the leading setup.
• Example product: - Weekly delivery — $25/order
• Monthly delivery — $90/order
• Quarterly delivery — $250/order

Maximum flexibility / custom rules

• WooCommerce Subscriptions is often the easiest to customize. It supports billing periods like every 3 months and multiple subscription configurations. WooCommerce

Enterprise

• Adobe Commerce or a custom headless stack can model complex subscription logic (different shipping dates, bundles, prepaid plans, etc.).

One important distinction: some platforms support billing cadence (charge every 3 months), but not true shipping cadence (ship weekly while billing quarterly, or consolidate shipments). If you need separate controls for when customers are charged vs. when products ship, look for a platform/app that supports separate billing and delivery schedules. Shopify’s selling-plan model explicitly separates billing and delivery policies. Shopify

If you tell me your store type (Shopify already? WooCommerce? custom?), product category, and whether “quarterly” means ship once every 3 months or pay quarterly but receive weekly, I can narrow it down.