Back to all articlesCampaign scheduling

Separate Promotions That Depend on the Same Inventory

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

Two campaign planners see the same stock. One schedules a loyalty offer for Tuesday; another schedules a public promotion for Thursday. Both plans look reasonable alone. Together, they may promise more inventory than the business can supply.

Before approving send times, approve shared stock commitments. Put competing promotions in one worksheet, assign one person authority over the pool, and make later sends conditional on a fresh reconciliation. Then choose whether to sequence, reduce, or defer each campaign.

A gap between messages is not enough. Customers can continue ordering after a send, and unrelated sales can consume the same stock. The control is not calendar spacing: it is a credible balance that includes fulfilled orders, unfulfilled commitments, and demand still expected.

1. Define the shared stock pool and calculation basis

Identify the exact item every promotion consumes. A loyalty reward, bundle, and public discount may use the same underlying product. Record the constrained variant rather than a total across sizes or colours. Translate bundles and multiple-unit orders into units of the constrained item.

For the opening plan, use:

Promotional capacity = verified physical stock − unfulfilled existing customer commitments − unusable stock − protected non-promotional allowance.

Here, physical stock means units still physically present, including any awaiting fulfilment. If your stock report already excludes allocated orders or unusable units, reconcile those exclusions first. Subtracting them again would understate capacity.

The protected allowance covers agreed ordinary demand and uncertainty. It is not automatically available to whichever campaign asks last. Every figure needs an owner and timestamp; uncertain counts should remain visibly uncertain.

This is a planning calculation, not a claim that software reserves stock. A commitment worksheet can guide decisions even when reservations and send controls require separate, authorised action.

2. Give the pool one decision owner

Campaign owners propose demand and explain priorities. They should not independently grant themselves the full stock balance. Assign four responsibilities, even if one person holds several:

  • Stock verifier: confirms quantities, count definitions, and discrepancies.
  • Stock commitment owner: approves allocations, releases unused commitments, and resolves conflicts.
  • Campaign owner: owns the audience, offer, demand estimate, and follow-ups.
  • Send operator: acts on an explicit release decision and records what happened.

Agree that a missing checkpoint means the dependent send waits. A booked slot, an earlier approval, or silence from the stock owner is not fresh authorisation.

Commitments also need review triggers. Finishing a send does not end demand, but keeping its entire allocation indefinitely can block other work. Release unused capacity only after reviewing open orders and plausible late responses.

3. Fill a shared worksheet before moving dates

Fictional worked example: All names, quantities, times, estimates, and decisions below are hypothetical. This is a recommended operating design, not an Alactic customer result or evidence of a product control. Each order uses one blue insulated bottle.

Filled artifact: opening stock and ownership

  • Pool and snapshot: blue insulated bottle; Monday, 09:00.
  • Physical stock: 1,000 units, including units awaiting fulfilment.
  • Existing unfulfilled customer commitments: 120 units.
  • Unusable stock: 40 units, still included in the physical count.
  • Protected allowance: 100 units for non-promotional demand and uncertainty.
  • Opening promotional capacity: 1,000 − 120 − 40 − 100 = 740 units.
  • Stock verifier: Priya, operations lead.
  • Stock commitment owner: Maya, commercial lead.
  • Send operator: Sam, campaign operations.
  • Missing-information rule: hold the next send until Maya records a decision.

Filled artifact: competing requests

  • A — Loyalty early access: Elena owns the campaign. Requested capacity: 400 units. Approved planning allocation: 340 units. Proposed send: Tuesday, 10:00. First in sequence, subject to a fresh check.
  • B — Public offer: Noah owns the campaign. Requested capacity: 300 units. Approved planning allocation: 240 units. Proposed send: Thursday, 10:00. Reduced scope; conditional on reconciliation after A.
  • C — Partner offer: Imani owns the campaign. Requested capacity: 200 units. Provisional allocation: 160 units. Proposed send: Friday, 10:00. Held until the post-B checkpoint.
  • Total requested: 900 units.
  • Total approved or provisionally allocated: 740 units.
  • Requested capacity removed: 160 units.

The opening conflict is now visible: requests exceed capacity by 160 units. Moving a send to another day does not eliminate that gap.

These allocations are planning ceilings, not enforced order limits. A reduced audience can still order more than expected. If the offer cannot be capped, use greater headroom, a smaller release, or deferral rather than treating estimated demand as guaranteed.

4. Test depletion and outstanding demand together

Before C, deduct both consumption already incurred and demand that remains outstanding. For this worksheet, outstanding demand has two parts: accepted but unfulfilled customer orders, and estimated additional orders from earlier campaigns. Keep those categories separate so an estimate is not mistaken for an accepted order.

The following hypothetical scenarios preserve the full 100-unit protected allowance. Additional leakage means stock losses or unrelated consumption beyond that allowance. The opening 120 customer commitments and 40 unusable units were already deducted when calculating the 740-unit starting capacity.

Filled artifact: C release scenarios

  • Lower depletion: fulfilled A consumption is 220 units; fulfilled B consumption is 180; additional leakage is zero. Remaining capacity before outstanding demand is 740 − 220 − 180 = 340. Unfulfilled A and B orders total 30; estimated additional A and B demand totals 30. Capacity available for C is 340 − 30 − 30 = 280 units.
  • Planning case: fulfilled A consumption is 300 units; fulfilled B consumption is 220; additional leakage is 40. Remaining capacity before outstanding demand is 740 − 300 − 220 − 40 = 180. Unfulfilled A and B orders total 25; estimated additional demand totals 15. Capacity available for C is 180 − 25 − 15 = 140 units.
  • High depletion: fulfilled A consumption is 340 units; fulfilled B consumption is 240; additional leakage is 100. Remaining capacity before outstanding demand is 740 − 340 − 240 − 100 = 60. Unfulfilled A and B orders total 15; estimated additional demand totals 5. Capacity available for C is 60 − 15 − 5 = 40 units.

Maya sets C's hypothetical release threshold at 200 units: its 160-unit plan plus a 40-unit margin. Only the lower-depletion case clears that threshold: 280 ≥ 200. Releasing C would leave 120 units beyond its nominal plan. The planning case, at 140, and high-depletion case, at 40, both fail.

These are decision scenarios, not forecasts with established probabilities. Their value is showing which assumptions change the release decision.

5. Reconcile a checkpoint without subtracting orders twice

Use a refreshed physical count as the basis for the actual checkpoint. Do not mix a current count with deductions for orders already shipped. The following filled reconciliation reproduces the lower-depletion scenario.

Filled artifact: Friday, 09:00 reconciliation

  • Refreshed physical stock: 480 units.
  • Consumption already reflected: the original 120 customer commitments have been fulfilled, along with 220 A orders and 180 B orders. Thus 1,000 − 120 − 220 − 180 = 480. Do not deduct those 520 fulfilled units again.
  • Unusable stock still physically present: 40 units; deduct now.
  • Accepted but unfulfilled campaign orders: A has 20 units and B has 10; deduct 30. These units remain in the physical count.
  • Estimated additional campaign demand: A may generate 20 more units and B 10 more; deduct 30. These are not yet accepted orders.
  • Protected allowance remaining: 100 units; deduct in full. No ordinary consumption has used it in this hypothetical checkpoint.
  • Available for C: 480 − 40 − 30 − 30 − 100 = 280 units.
  • Decision: 280 meets the 200-unit threshold. Maya authorises C's 160-unit plan; Sam records the release before sending.

The two calculations agree because they use the same assumptions. The scenario rolls forward the opening capacity; the checkpoint starts from current physical stock and deducts only remaining obligations and protection.

When a forecast order becomes an accepted order, move it between categories rather than counting it in both. When that order is fulfilled and leaves physical stock, remove its unfulfilled commitment too. If ordinary sales consume protected units, reconcile both the lower stock count and the remaining allowance explicitly.

6. Record a conditional sequence, not just send dates

Choose order using a stated business priority rather than calendar ownership. In this hypothetical example, Maya prioritises loyalty access, reduces the public offer, and keeps the partner offer conditional.

  1. Tuesday, 09:00 — check A: Priya refreshes the stock basis. Maya confirms support for A's 340-unit allocation before Sam releases it.
  2. Wednesday, 15:00 — reconcile A: Elena separates fulfilled orders, unfulfilled orders, and estimated additional demand. Maya approves any release of unused allocation.
  3. Thursday, 09:00 — decide B: after deducting outstanding A demand, available capacity must cover B's 240-unit allocation. Otherwise Maya requires a reduced proposal or defers it.
  4. Friday, 09:00 — decide C: after deducting outstanding A and B demand, at least 200 units must remain. If not, the original send stays held.

A smaller replacement for C needs its own demand estimate, margin, and approval. It should not automatically consume whatever balance remains.

Use checkpoint intervals that produce useful information. Sequencing helps when earlier demand becomes clearer before the next release. It offers little protection when responses overlap and nobody estimates the remaining demand.

7. Choose reduction or deferral when timing cannot solve it

Reduce when the campaign still serves its purpose at smaller scope. Narrow the audience or remove a follow-up, then revise the unit estimate. Recipients and stock units are different measures; document the assumption connecting them, including multiple-unit orders where relevant.

Defer when stock cannot be verified, outstanding demand is too uncertain, or the offer cannot be meaningfully reduced. Give deferral a review trigger, such as reconciliation of earlier orders, rather than an indefinite instruction to check later.

Keep inventory release separate from channel readiness. For WhatsApp, recipient permission matters and opt-outs must be honoured. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements, and provide a clear human escalation path for automation.

Campaign preparation, template review, inventory authorisation, and actual delivery are separate states. None substitutes for another. If using Alactic, check the workspace and current plan for availability rather than assuming a CRM practice is a Communications feature or that a web capability exists in the Android app.

8. Replace stale approvals and inspect the outcomes

If stock changes after approval, hold unreleased dependent sends while the discrepancy is assessed. Refresh the balance using the same basis, then record the replacement decision, owner, time, and reason. Tell affected planners which earlier approval is no longer valid.

Include reminders, follow-ups, and other channels in the reassessment. Adding a reminder changes the demand plan even if the main send date stays unchanged. Messages already delivered cannot be treated as recalled; route affected customer conversations to a responsible human team.

At the next scheduling review, inspect observable outcomes:

  • Did every released send have a current stock snapshot and named authoriser?
  • Were fulfilled orders, open commitments, and forecast demand kept separate?
  • Did each conditional send receive a recorded proceed, reduce, or defer decision?
  • How did actual depletion differ from the estimate, including late responses?
  • Were unused allocations explicitly released rather than silently reassigned?

The worksheet succeeds when it changes a decision before stock is overcommitted. Start with one shared pool and one accountable owner; make the next dependent send earn its release through a reconciled balance.

Campaign schedulingInventory planningCampaign operations

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications