This network-only screen stores storefront revenue policies. It does not assign credit to an individual associate, arbitrary location, marketing channel, or receipt source, and it is separate from saved-sale attribution audit events.

Before you beginUse an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.

Step by step

  1. Go to Admin → Revenue attribution. Confirm you are in the intended network tenant; the page loads policies owned by the current tenant and child tenants whose parent is that tenant.
  2. Read every policy card before adding one. Each card shows its name, whether it is inactive, whether it applies to All franchisees (default) or one specific child, and the HQ-fulfilled and locally fulfilled model values.
  3. Choose New policy. Enter a clear Policy name and set Applies to to All franchisees (default) or one exact child organization. The screen does not explain precedence when several active policies overlap, so avoid ambiguous duplicates unless downstream policy resolution has been separately verified.
  4. Under When HQ/factory fulfills, choose HQ keeps revenue, HQ keeps revenue + franchisee gets credit/rebate, or Split revenue.
  5. If using franchisee credit/rebate, choose No rebate, % of order, Flat $ per order, or Flat $ per unit. Enter Rate only when the rebate type is not None.
  6. Under When franchisee fulfills locally, choose Franchisee keeps revenue, HQ keeps revenue (pays commission), or Split revenue.
  7. If HQ keeps locally fulfilled revenue, choose No commission, % of order, or Flat $ per order. Enter Rate only when the commission type is not None.
  8. Under Additional settings, enter Cost-plus markup % for product cost on inter-company transfers. Choose whether accumulated credits offset royalty invoices and/or reduce network transfer invoices for product purchases from HQ.
  9. Choose Save and wait for Revenue policy saved. Reopen the card and verify every stored field. The current editor does not expose an Active switch or Notes field even though those values exist in the record.
  10. Use Edit for an existing policy. The trash action deletes immediately without a confirmation dialog in this implementation, so treat it as a destructive action and verify the exact policy before choosing it.
  11. Validate with a controlled storefront/WooCommerce order whose fulfilling party and child organization are known. Reconcile the resulting network economic records, rebate/commission or split, and any credit offsets; a saved policy alone does not prove the downstream order applied it.

Screen and contract reference

Control or areaWhat it means
Policy scopeEither all child franchisees as the default or one selected direct child tenant.
HQ/factory fulfillsThe order is fulfilled by HQ or the factory; the policy chooses HQ revenue, HQ plus a child rebate, or a split model.
Franchisee credit/rebateHQ retains revenue while the child receives the configured percentage, per-order amount, or per-unit amount.
Franchisee fulfills locallyThe child fulfills the storefront order; the policy chooses child revenue, HQ revenue with commission, or split.
Local commissionPayment to the fulfilling child when HQ retains revenue: percentage or flat per order.
Split revenueA stored revenue-model choice. This editor does not expose a split percentage or allocation fields, so verify the downstream implementation before relying on an amount.
Cost-plus markupPercentage added to product cost for inter-company transfers.
Credits offset royaltiesAccumulated policy credits reduce franchise royalty billing.
Credits offset product ordersCredits reduce network transfer invoices for product purchases from HQ.
Inactive badgeThe stored policy has is_active false. This editor displays the state but currently provides no control to change it.
Notes boundaryThe policy record supports notes, but the current editor does not expose a Notes input.
Delete boundaryThe trash action deletes the policy immediately and has no confirmation dialog on this screen.
Proof of attributionA reconciled controlled storefront order and its network economic records, not merely the successful policy save message.

Expected result

The intended user, location, channel, or source receives credit under the configured rule, and a controlled sale’s attribution agrees across receipt and reporting views.

Troubleshooting

  • Confirm you are changing the intended business and location before saving.
  • Record the previous setting when a change affects live selling, payments, tax, or integrations.
  • Use a controlled test record after saving before rolling the setting out broadly.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.