Reseller workspace

A reseller credit buys whatever the supplier’s panel defines for that account. Find the deduction for the customer’s exact term, the complete purchase price and the credits you can actually spend. Then put a single account through the full workflow. Confirm the device, activate the agreed term, check the expiry, and reconcile the debit. A pack comparison becomes useful once those steps agree. If one step remains unresolved, a bigger purchase gives you more of the same uncertainty to manage.

This guide follows one cycle from quote to renewal. The named rate examples come from provider-published schedules and are dated. The planning, ledger and support examples are fictional. Start with the stage you are at and keep its output in your own records. You should be able to trace a customer term to a quote, a panel movement and a confirmed expiry without opening a chat thread from three months ago.

Establish what you are being offered

Ask the seller to identify the business issuing the quote, the exact service or account type, and the domain you will use for panel access. Keep the reply and the invoice details together. If the invoice comes from a different name, ask for the relationship in writing and verify it through a contact already associated with the original business. The same principle applies to a new payment address. Confirm a change using the contact you had before receiving the instruction.

Write down the territory, intended use and account scope. A home viewing subscription, a player licence, and a right to sell accounts are three different purchases. A panel may be able to generate a line in seconds while the business still needs a written basis for supplying it to that customer. Ask who authorizes resale, which markets and customer types are included, and who resolves complaints about carriage or access. A readable quote and an independently traceable counterparty matter more here than a polished screenshot.

Check the programmes the customer actually wants. For a sports customer, ask for the competition, fixture, market and whether they expect live coverage or highlights. A league may list different broadcasters by territory and separate live, audio and highlight rights. Its published broadcaster list is a better starting point for checking the specific event than a total channel count. When a customer asks for an event you cannot verify, describe what you can confirm and keep the event out of your promise. Premier League broadcast rights FAQ · Find the broadcaster for a specific live match

Next separate the player from the account. A customer could already have paid for an app and still need the correct viewing entitlement. Another might have an active account and a television that lacks the supported player version. Ask for the full hardware model, operating system, app publisher and version before committing to setup. A trial on your phone tells you little about the customer’s TV if the app differs. Save a short list of confirmed combinations and the date you checked them. Player and viewing account guide · Provider directory

Ask for a quote you can put in a spreadsheet

A workable quote answers concrete questions. Start with what is included in the total, when the price expires and how many credits become usable. Ask whether the pack requires a panel opening fee or a continuing minimum purchase. If bonus credits are offered, check whether they have the same term deductions, expiry, renewal eligibility and reversal rules as the credits you paid for. Record each condition with the relevant offer. Two numbers that share a currency can still describe different purchases.

Phrase the important questions as a small scenario. Ask what happens if you renew an active three-month customer today with ten days left. Ask the supplier to give the exact credit deduction and the new expiry date for that case. Then ask how it changes when the line has already expired. The answers tell you more than a claim about flexible renewals. Save the wording with the quote date so a staff member can check the same rule later.

Request a copy of the movement or invoice format before building a large workflow around the panel. An activity log needs a stable ID for each debit and reversal. A downloadable record should make it possible to track the date, credit amount and linked account after a member of staff leaves. If the panel provides only a current balance, agree how support will supply historical movements. Build your own order log from day one while the volume is manageable.

Read the terms attached to the actual role. A wholesale pack enquiry can tell you the cost and allocation. A distributor arrangement adds responsibilities for ongoing sales, approvals, support and access to customer records. Treat any promised territory, child account or volume pricing as a specific written term. You can ask for those terms without signing up for a larger role. Wholesale research · Distributor research

Compare equal customer terms across different credit systems

Divide the full billed amount by the usable credits in the pack to get a unit rate. Multiply that unit rate by the stated deduction for the customer’s term. If you need the cost per customer month, divide the resulting term cost by the number of months in that term. Keep the original quantities and total beside your calculation. Carry the full rate through the calculation and round the displayed result.

The examples below use the smallest published pack shown by each of two providers. Both are USD schedules checked on 13 November 2026. Trex publishes a customer-month model. Pro Max publishes fractional deductions for shorter terms and a whole credit for an annual term. The columns describe base credit cost, using the source rate and the stated deduction. Trex reseller schedule · Pro Max reseller schedule

The pack counts look far apart at 60 and 10 credits. For annual customers, these packs would cover five and ten complete terms respectively under their published rules. For the Pro Max pack, ten divided by 0.3 gives 33 complete three-month terms and 0.1 credit left. That last tenth can meet a one-month deduction under the same schedule. The capacity assumes a fresh balance, no holds and the listed customer type. Use the same term and entitlement before looking at cost, then keep the upfront pack amount in a separate column.

Strong 8K’s published starter pack contains 120 customer-month credits for USD 222.00. Its annual allocation is 12 credits, or USD 22.20 at the published starter rate. That equals the annual arithmetic for the smallest Trex pack in the table even though the Strong 8K starting purchase is twice the cash outlay. The supplier identity, account terms, support and authorizations still need their own checks. Strong 8K starter pack · Credit comparison worksheet · Credit calculator

Watch for conflicts between a provider’s published price lists. On 13 November 2026, Golden OTT’s reseller pricing page and its public card catalogue showed different quantities and rates. The pricing page showed a 60-credit pack at $95.40, or $1.59 per credit. The card catalogue showed a 10-credit pack at USD 139.00, or USD 13.90 per credit. Keep both references on the enquiry. Ask which schedule applies to the issued panel, confirm the currency and get the actual term deduction before building a comparison. Golden OTT pricing page · Golden OTT reseller cards · Golden OTT enquiry worksheet

Buy for committed work and know what will remain

List confirmed renewals and new orders by supplier, panel and term. Use the expiry date to order the renewals. Put undecided quotes on a second list and keep test allocations, staff trials and any holdbacks visible. A customer asking about next month belongs on a different line from someone who already agreed the term and payment. This keeps an optimistic forecast from consuming the balance you need for existing commitments.

Suppose a fictional first batch uses the Trex customer-month schedule for seven annual terms, five quarterly terms and four monthly terms. The arithmetic is 84 + 15 + 4, or 103 credits. One 120-credit pack at the published USD 214.80 total covers the batch and leaves 17 credits. Two 60-credit packs would cover the same work at USD 222.00, assuming the purchases can be pooled in the same account. A 300-credit pack at USD 507.00 leaves 197 credits and requires USD 292.20 more upfront than the 120-credit pack. That difference is a purchase decision, even if every eventual credit in the larger pack is cheaper. Trex published pack prices

Write a second plan for a slow month. Which orders could fall through, and how many credits would you still hold at the next statement date? Find the next balance checkpoint before buying more. A reasonable point is just before a renewal cluster or before a supplier’s quoted top-up window ends. If unused units expire or a purchase minimum applies, those terms change the timeline. Keep committed units, forecast units and untouched balance in separate columns.

For a pack you are already using, estimate the next buying threshold from due renewals plus a buffer you explicitly set. Imagine 98 usable credits, 91 credits of accepted renewals before the next delivery date and an eight-credit operating reserve. Free balance for those renewals is 90. You are short one credit relative to the chosen buffer, even though the panel’s balance looks healthy. Resolve the actual timing and reserve decision first. A smaller valid top-up, a shorter supplier lead time or confirmation of a postponed renewal could each change the need. Keep the terms the customers already agreed.

Keep inventory cost and customer money separate

There are two totals in a credit purchase. One is the amount paid to the supplier today. The other is the portion you allocate to the customer work you actually complete. If you mix packs that share the same credit unit and account, preserve the history. For a planning calculation, divide the combined purchase cost by the combined usable quantity for a weighted unit cost. If credits are kept in separate balances or expire at different times, maintain those balances independently so you can see which one funded each action.

Here is a fictional mixed batch based on the public Pro Max schedule. Ten credits at USD 228.90 plus 25 at USD 547.50 give 35 credits for USD 776.40. That is USD 22.182857… per credit on a weighted planning basis. Ten one-month activations use 1.0 credit. Four three-month activations use 1.2. Two six-month activations use another 1.2 and three annual activations use 3.0. The batch uses 6.4 credits, about USD 141.97 allocated at the unrounded rate, and leaves 28.6 credits. The supplier received USD 776.40 for the two packs. Pro Max published pack and deduction schedule

Track the customer-side work in a different ledger. For a fictional USD 36.00 annual order, suppose the term uses USD 21.48 in credits, the processor fee is USD 1.38, setup and support time is valued at USD 5.50 and the operating reserve is USD 2.00. The remainder under those assumptions is USD 5.64 before any other costs. If a second support appointment adds USD 6.50, the same scenario falls to minus USD 0.86. A sensitivity check like this shows which cost to watch on similar orders. Use the actual processor settlement, refunds and other costs in the wider ledger. Work through reseller term costs

Keep supplier invoice currency and customer payment currency visible where they differ. Use the actual amount charged and any conversion fee from the settlement record. If you are preparing an estimate from a current exchange quote, date it and retain the original currency. That lets you review what changed after settlement. A bank fee charged on the pack and a per-customer payment fee belong on their own lines.

Confirm the panel can perform a full customer lifecycle

Ask for a demonstration within the proposed role, preferably with a test account the provider authorizes. Start with a visible balance and a known expiry state. Create a permitted test term, identify the movement ID, read the resulting expiry and check the account on one supported device. Ask how the same action appears in exports and what happens if it is interrupted. A screen recording from an admin account can show the broad interface. A role-specific demonstration shows which controls you would actually receive.

Choose the exercise to match how you work. An operator doing renewals needs to find an existing account safely and verify a term. A support user may only need the expiry and status. The person responsible for purchasing needs the ability to match an invoice and a credit movement. Ask the supplier to show each permission with a named role. Then keep your own small permission register as staff and responsibilities change.

Try the first installation on the kind of device your customers use. Record the exact model and software. Fire TV devices, for example, can differ in their OS family across generations with similar names. Use the manufacturer’s model table, then compare the player’s own publisher listing. Establish what happens when a trial works on the test phone but the customer’s television has a different player or storefront. Agree who helps with that step before giving a customer a start date. Amazon device specifications · Fire TV model and OS guide · Trial testing checklist

Finally, verify the route for problems you cannot resolve yourself. Ask who handles a stuck debit, a missing entitlement and a report about carriage. For each, keep a known contact channel and the expected information to submit. A one-time test can confirm that you know where to report an issue. Record response time only when you have actually observed it and distinguish the provider’s written commitment from one observed outcome.

Carry one order from agreement to a verified expiry

Start with a unique internal reference. Store the quoted product, term, currency, connection allowance, device and expected start. The same reference follows the payment, the panel action and any later correction. Use a separate field for the supplier movement ID. Panel actions may be recorded in a different order from the payments, especially when staff work in shifts. Keeping the identifiers together gives a second person enough information to finish the order safely.

Verify the payment in the processor or your authorized settlement record. When an order is pending, record the last status and the time checked. A customer can return from checkout before an asynchronous payment finishes. Stripe’s documentation, for example, distinguishes a processing state from a completed payment. Use the statuses and verification route for your own processor. When the two records disagree, match the amount, currency and transaction ID, then leave the provisioning state open while the payment is confirmed. Stripe payment status lifecycle

For a new account, check that the selected product and account region match the quote. For a renewal, use the existing private account reference and write down its current expiry first. Confirm the proposed term, expected debit and expiry rule before submitting. Ask staff to reserve or claim the work item in your own queue so two people do not process it together. Record what the panel shows after submission while the screen is still open.

For a fictional customer whose annual line expires on 26 November, a provider might extend from 26 November if staff renew early. Another account type could begin its new term when the operator submits it. Some panels display a time and zone alongside the date, and others display only a date. Use the provider’s written convention to determine the expected result. If the old expiry is still in the future, ask what happens to the remaining entitlement before taking payment for the renewal. The customer should know the period they are agreeing to buy.

If the panel times out after submission, look for the action in its movement and customer history before repeating it. Compare the old and current expiry, the account status and the exact debit. An unchanged page can lag behind the recorded transaction. A movement without a new expiry needs a supplier check. In either case, mark the order as needing review and write down what would count as confirmation. This gives the next operator a defined decision instead of a free-form instruction to try again. Strong 8K renewal verification example

Reconcile usable and posted balances before the next top-up

Choose a period with a known opening balance and record the time zone of both endpoints. Include purchases that posted within the period, posted debits and credits that returned through a confirmed reversal. Keep reservations in a separate view. A panel can show an available balance that already excludes a hold while its transaction list only includes posted movements. Use the provider’s definitions to compare like with like.

The following is a fictional account with fractional movements. Numbers below describe credits. The order IDs are examples.

If request E reserves 0.6 credits and is the only hold, the expected usable balance is 38.1. A screen showing 38.1 available and 38.7 posted would agree with the ledger. If the export instead reports 38.4 posted, check whether the reversal reached the statement cutoff. Keep a note of any reversal expected after the cutoff. Record it when it posts and keep its link to the original debit.

There are a few useful patterns when a balance differs. A debit twice the expected amount can indicate duplicate actions or a different term rule. A difference equal to a single pending request can come from a reservation. An exact missing top-up calls for the supplier order number and payment confirmation before you assume there is a credit shortage. Investigate one specific movement at a time. A manual correction with no explanation can conceal the original cause and make next month’s opening balance hard to justify.

Use one row per posted movement, even if several movements relate to the same order. A customer refund, a supplier reversal and a return of reserved credits can occur at different times or in different systems. Record the reason and the link between the entries. If a refund was paid to the customer and the supplier denied a credit reversal under the quoted terms, both outcomes belong in the record. Closing the customer ticket leaves the supplier-side balance unchanged until a movement posts. Reseller balance reconciliation guide

Protect the accounts that can spend credits

Give each staff member an individual sign-in when the panel supports it. Assign the smallest role that covers their task. The colleague checking expiries can use a role with a read-only customer view where one exists. Staff who handle renewals need a role that permits extension and shows the associated debit. Reserve bulk exports, pack purchases and changes to recovery settings for whoever owns those responsibilities. Ask which activity is recorded by user and how you can review it. Microsoft guidance on least-privilege roles

Use multifactor authentication where available, and document the recovery route for privileged accounts before depending on it. Keep recovery material in the authorized secure store and give access to the people assigned to recover the account. A shift handover can include the work list, due renewals and pending support references without handing over a password. Keep the list current as responsibilities change. CISA multifactor authentication guidance · Panel handover checklist

If the supplier only issues one master login, ask how individual users can be assigned safely before sharing work. A small team can keep a single named operator for privileged panel actions and let other staff handle customer checks in their own system. Record who can take over when that operator is away. If access is lost, confirm the recovery contact against earlier records and reconcile recent activity once the account is restored.

Keep the order and support log lean. In an internal record, store the private reference, term, expiry, customer contact details needed for the job, and what the operator did. Avoid putting access credentials in free-text notes. Use the provider’s designated private route for any identifier it genuinely needs. For forum help, use an invented customer label and redact account fields, playlist addresses, portal tokens, contact details and payment information from images. Review the full image, including open tabs and notification previews. The European Commission’s explanation of data minimisation is a reference for limiting the personal information you retain. European Commission on data minimisation · Forum rules

When an operator leaves, revoke their individual access, review the remaining role list and check the active recovery contacts. If credentials were shared with that operator, use the provider’s authorized process to rotate them and review active sessions and recent movements. Keep copies of the private ledger under the business account. Check that a second authorized person can read the order history and continue the work without asking a former colleague for a screenshot.

Triage support with one good observation at a time

A customer report usually arrives as “it stopped working.” Ask what they were trying to do when it failed. Did the player reject a sign-in, load an empty channel list, open a video that buffered, or show the wrong programme times while the video still played? Write the observation in the customer’s words, then run one check that separates the likely causes. A playback failure, a guide mismatch and a panel debit can happen on the same day and still need different investigations.

Imagine two customers report a freeze during the same evening. One uses a television app that stalls on one regional feed. The other sees the guide off by an hour on a different device and can watch live channels. Keep separate tickets while you check each observation. Run the first feed against a known control on the same TV. For the second, match one published programme with the exact feed, zone and time. If the first test indicates a feed problem and the second a mapping issue, send each to the contact who can act on that evidence. Controlled buffering test · Fix a one-hour guide offset

When escalating an order, give the supplier one event it can look up. Include the private order and movement IDs, account term, time with zone, expected outcome, observed outcome and any control result. State which action has already been tried so support can check the existing movement. Ask for a precise reply, such as confirmation of a posted reversal or the new expiry. Summarize the result for the customer in plain language, and give a next update time you can actually meet.

For public forum help, post the reproducible symptom without the customer identifiers. Keep the device, software version, time zone and safe control result. If several customers show the same symptom, check that the product, source, device or time period truly overlaps before combining cases. A single good observation can save an afternoon of speculative app reinstalls. Reseller forum category · Find support

Use a short handover that another operator can follow

At the end of a shift, list the renewals due before the next handover, the orders awaiting confirmed payment, the panel movements awaiting a matching expiry and the support cases that need a reply. Write the next action for each. Keep confirmed work in the ledger instead of copying it back into the handover. If a batch will use a large share of the balance, reserve its credits in the work queue and name the operator who will check the result.

For a fictional Friday close, suppose three annual renewals are agreed, one three-month order is waiting for the customer and a test request has reserved 0.6 credits. If the supplier’s annual deduction is 1 credit, schedule 3.0 credits for the renewals. Leave the unconfirmed order on the quote list. Carry the test hold forward with its request reference. On Monday, confirm which actions posted before asking the supplier for a top-up.

Review one completed order regularly with a second person. Start with the quote, find the recorded payment, locate the debit, and read the confirmed expiry. Then trace one unresolved case and check whether its owner and next update are obvious. If a field keeps going missing, change the order form or handover sheet so it is collected at the point of work. A good record describes what happened well enough that the next operator can act without repeating a customer’s entire setup.

As the work grows, check the current supplier rules again before promoting a new term or adding a distributor role. Save the evidence alongside the service guide you give staff. Verify changes on a test account when permitted. Keep previous quotes with the orders they covered, and apply updated rules to future quotes from their documented effective date. That record makes it possible to explain why two customers renewing on different dates received different terms.

Handle supplier changes around existing commitments

Prepare for the ordinary changes first. A supplier may issue a revised catalogue, a player developer may retire an app version, or a credit package may acquire an expiry date. Find the first date the new rule applies and ask whether it affects credits you already hold, open quotes, future top-ups or active accounts. Save the response beside the supplier’s previous terms. An operator can then check an order against the terms in effect when the customer accepted it.

Consider a fictional supplier who changes the deduction on a new annual term from 1.0 to 1.2 credits on 1 December. You have 12.0 credits on the statement. If all 12.0 credits can still be used and the new rule applies to every annual activation in December, the balance covers ten annual terms. Six annual renewals already agreed would take 7.2 credits and leave 4.8, enough for four more under the same assumptions. If the supplier instead preserves the old deduction for certain orders, tag each qualifying order with its quote date or other qualifying fact before making the calculation. Keep a written record of that scope.

Plan around the customer date when a device change is the problem. If the player’s publisher announces the end of support for an older television, identify affected model groups from your setup records. Confirm what the publisher currently offers on one representative device you can use, and note the date and operating system. Contact the customers whose confirmed setup depends on the older build. Give them the verified route, what they need to bring to the support appointment and who will handle the update. A notice aimed at the actual device group helps the person receiving it decide whether to act.

Write down what happens if a supplier pauses new activations or if account access becomes uncertain. Check the provider’s status and find the committed orders most affected. Start with renewals that have accepted payment and expire soon. Where the supplier confirms an existing entitlement remains active, record that confirmation and use the next verifiable checkpoint to decide the customer update. Hold new commitments that depend on unavailable provisioning. If the customer’s order needs a change or cancellation, follow the agreed order terms and record the separate customer and supplier outcomes.

For a possible move to another supplier, verify the territory, product scope, device fit and customer agreement from the start. Take one permitted account through the new workflow while the old order history is still available to you. Compare a live feed, one guide example and the connection allowance the customer needs. The customer’s old account expiry and any credit balance may follow entirely different rules. Preserve the old references for open support and refunds, and ask both providers to identify any supported migration in writing. Provider comparison worksheet · Wholesale research

At the next ledger close, review how many credits remain with the old supplier, which orders are waiting on a correction and when customers last received a useful update. Assign a named person to each open case. A handover that includes those three facts gives the next operator a way to finish the outstanding work even if the supplier relationship has ended.

Four questions to answer before buying the next pack

What will these credits buy in my issued panel? Get the deduction for each accepted customer term and record when the credits become usable. An offer that describes only the size of the pack leaves the capacity unknown.

Can I trace a renewal from payment to expiry? Use one internal order reference and record the processor status, supplier movement and verified expiry. Hold uncertain actions for review until you can identify the original result.

What happens to unused or reserved credits? Get the expiry and release rules in writing. Compare posted balance with usable balance before ordering more. Keep new purchases and pending reservations visible in different fields.

Who handles the next problem? Write down the route for payment, panel and playback issues. Make sure the person on duty has enough access to see the necessary evidence and a clear way to ask the supplier for help. Credit calculator · Provider comparison · How the forum reviews provider evidence