Recurring orders FAQ
What to know about recurring orders.
Clear answers on scheduled reordering, buyer-managed standing
orders and ERP-connected repeat demand for Shopify Plus teams
using systems like Pronto Xi, Microsoft Dynamics 365 Business
Central, Apparel21, Exact or Oracle E-Business Suite.
What is a recurring order in Pocketknife?
A recurring order is a saved B2B order schedule with products,
quantities, frequency and next order date. It helps your team
support standing orders without rebuilding the same cart
manually.
Can customers change quantities or cadence?
Yes. Customers can adjust line quantities, frequency and next
order date, so the schedule stays useful as their demand
changes.
Can recurring orders be paused or resumed?
Yes. A recurring order can be paused when the customer does not
need the next run, then resumed without deleting the schedule.
Can recurring orders use customer-specific pricing?
Yes. Recurring orders can use the same customer account,
catalogue and pricing context as the rest of the Pocketknife
portal, so repeat orders stay aligned with B2B terms from
Shopify and your ERP.
What happens when a recurring order is due?
When a recurring order is due, Pocketknife can create the next
order from the saved schedule and keep the order connected to
the normal Shopify and ERP workflow.
Can a customer reorder immediately outside the schedule?
Yes. The customer can use reorder now when they need stock
earlier, while the recurring schedule can still calculate the
next future run.
Can recurring orders be created from an existing order?
Yes. Recurring orders can be started from an existing order so
customers do not need to rebuild the same product list from
scratch.
Can we see upcoming recurring orders before they run?
Yes. Upcoming next order dates help your team see repeat demand
before the order is created.
Can customers edit recurring order line items?
Yes. Customers can adjust line quantities and keep the saved
schedule aligned with what they actually need.
Can a recurring order have delivery instructions?
Yes. Delivery instructions can stay attached to the recurring
order so repeat fulfilment does not rely on memory or email
notes.
Can recurring orders be limited to eligible customer accounts?
Yes. Eligibility can be checked against account rules, such as
whether a customer location can create orders on account.
Can recurring orders be filtered by customer or status?
Yes. The recurring orders view can support search, customer
filters and status filters such as active or paused.
Can we view recurring order history?
Yes. Recurring order history can show prior runs, order totals,
statuses and ERP order numbers where available.
Can recurring orders include shipping costs?
Yes. Shipping lines and totals can stay attached to the
recurring order so your team and customers understand the
expected order value.
Can recurring orders sync with ERP order workflows?
Yes. Orders created from a recurring schedule can flow through
the same Shopify and ERP order handling used by other B2B
orders, including workflows connected to Pronto Xi, Microsoft
Dynamics 365 Business Central, Apparel21, ASW, Exact or Oracle
E-Business Suite.
Can customers receive reminders before a recurring order runs?
Yes. Reminder timing can be configured so customers or your team
have time to review a scheduled order before it runs.
Can our team pause recurring orders for customers?
Yes. Your team can help manage schedules, pause orders, resume
orders or update details on behalf of customers when they have
permission.
Can recurring orders reduce customer service workload?
Yes. Customers can manage repeat orders themselves, which
reduces repeat phone calls, emails and manual order entry for
your team.
Can recurring orders work for weekly and monthly buying cycles?
Yes. Recurring orders can support daily, weekly or monthly
intervals depending on how you want to offer scheduled
reordering.
Can recurring orders help prevent missed replenishment orders?
Yes. A saved schedule helps customers keep essential products
topped up and helps merchants avoid missed repeat revenue.