You can bring together billing for devices in your Plaspy account, equipment on other platforms and phone lines in Plaspy’s My customers. This lets you represent the customer’s commercial relationship without first moving every tracker. External equipment and lines remain references: adding them does not connect their systems or carry out their renewals.
The question often arrives more simply: “What am I paying you for?” The customer may have vehicles on different platforms and a phone line you also supply. Answering clearly means explaining those services and their terms, even when they are operated through different systems.
Bringing that explanation together is useful work. To do it well, establish what a subscription includes, which quantity determines its price and which action still belongs with another provider. A common commercial reference then retains a meaning both your customer and your team can understand.
The commercial relationship can be organized while devices stay separate
With a mixed customer base, the relationship with your business can continue across different tools. A customer might use Plaspy for some vehicles, another platform for others and an operator for mobile service. Billing needs to connect those parts to the agreement without turning them into a single technical installation.
The Subscriptions guide provides for three item types. A Plaspy device is selected from the equipment in your account. An External id identifies equipment outside Plaspy through its IMEI, serial number or another reference. A Phone line represents the number of a line the customer pays you for. Each type’s meaning matters when explaining what you administer.
The subscription brings together its description, price, period, Paid until date and covered items. That structure identifies the commercial agreement and its renewal date. The external reference helps recognize the service, but does not bring its positions onto the Map or establish an administrative connection to another platform. The information being brought together concerns billing.
This separates two decisions that can become mixed up in a customer conversation. You can organize services you charge for without having decided to migrate their tracking. A migration, if considered later, needs its own technical and commercial review. Creating an external item does not establish that migration has happened or replace checking a device’s compatibility.
There is also no need to present every combination of providers as a problem that must disappear. Some agreements may continue across multiple systems. What matters is knowing which service you charge for and where each administrative action continues. Organization becomes useful when it helps answer the customer without inventing an integration the record does not provide.
Three vehicles can mean more than three chargeable items
Consider an entirely fictional example. A company has three vehicles: two trackers are managed in your Plaspy account and the third through another platform. You also charge it for three phone lines, one per vehicle. For this example, one subscription contains two Plaspy devices, one external identifier and three lines as separate items.
There are three physical vehicles but six items: two plus one plus three. Suppose the agreement also uses the same period for these services and an invented price of USD 10 per item. With per-item charging enabled, the calculation is six times ten, or USD 60 for that period. Multiplying three vehicles by ten gives USD 30, but uses a different unit.
These amounts are not Plaspy prices or suggested rates for your business. Nor do they mean you should charge twice for the same service. We have defined separate services represented by separate items under a particular pricing condition. Before judging the total, establish whether that representation matches the actual agreement.
Here, USD 10 is the reseller’s selling price per item to the customer for the assumed period. It does not represent the platform licence cost or the operator’s invoice to the reseller. This commercial record describes what the customer pays your business. It does not independently calculate the agreement’s profitability or settle the amounts you owe your own suppliers.
The lines make the distinction clearer. A phone number appearing as a device detail does not, on its own, create another Phone line item. Our example explicitly states that you added three lines as items. Explaining the charge means counting what appears in that item list, rather than inventing additional elements from every visible detail.
A fixed amount represents another way of expressing the price. When the subscription is not charged per item, its amount applies to the subscription as a whole. Reading only the plan name or vehicle count therefore leaves an important part of the explanation open. Examine both what is covered and how the price is applied.
This has a concrete commercial consequence. If the customer understands a per-vehicle fee to include its phone line, the price and items need to represent that agreement coherently. If they pay for separate services, those should be recognizable too. The administration screen does not decide what you sold; it lets you examine how the agreement was represented before communicating the amount.
One customer record does not require one period for every service
Keeping services within a customer record makes the relationship recognizable without forcing every service to have the same terms. One customer can have several subscriptions. Each retains its own period and date according to the service being charged for. The customer is shared; the particular commitments may need different representations.
For example, if one service renews annually and another monthly, putting them under a general description does not fully explain both renewals. A subscription uses a period to advance Paid until. When agreements have different frequencies, their organization needs to preserve that distinction instead of treating one date as an explanation of everything.
This is not a reason to repeat a calculation of several years’ costs or derive a monthly average here. The question is which renewal corresponds to each moment. The article on organizing customers and subscriptions develops that relationship. Here, its application matters because some services continue operating outside Plaspy.
The description helps the customer too. According to the documentation, it appears in messages and on the payment page; an empty description uses the plan’s name. A phrase such as “various services” can group items correctly while still making the renewal hard to recognize. A familiar description helps continue the conversation about the relevant agreement.
Reminders follow the subscription’s Paid until date and require prepared rules and channels. Sharing a customer record does not turn every service into one due date or create a general notice that replaces all other renewals. The expiry reminder help retains the configuration details for those communications.
The organization should support a precise answer when a customer asks about a notice after paying for something. First identify which service each reference concerns. This does not assume another payment is needed, or that one payment automatically covered every subscription. The agreement and the particular transaction continue to give the date its meaning.
One payment does not perform every external action
Take another fictional situation, separate from the three vehicles above. A subscription contains one Plaspy device, one External id and one Phone line. Renewing extends the linked Plaspy devices is enabled. Suppose the external service and phone line had previously been suspended by their providers, under their respective agreements and through those providers’ own procedures.
The customer now makes a payment that is confirmed and renews this subscription. Plaspy records the transaction and applies the relevant renewal to its associated device under the stated configuration. The External id and Phone line keep their role as references. That payment does not independently constitute a reactivation instruction sent to the other platform or operator.
In this example, the outcome of the external actions still needs establishing. A note saying “reactivate” can describe outstanding work; it does not establish that the provider performed it. Similarly, receiving a payment notice informs you of the commercial transaction without automatically confirming a procedure completed in another system.
This matters when responding “everything is ready again.” A checked commercial renewal and an outstanding external action can coexist. Explaining those services’ availability requires the relevant references and the person authorized to manage them. The example does not describe a particular operator’s deadlines, rights or procedures, and does not propose suspending a line.
The distinction works in the other direction too. An external service remaining available does not establish that its commercial subscription is paid. The provider might have different terms, or the administrative action might not have occurred. Service operation and billing information answer connected questions, but they cannot simply substitute for one another.
This scope gives Plaspy a concrete role. You can bring together the renewal charged to your customer and retain references for external elements. At the same time, establish where to verify the work My customers does not perform. A central record is more useful when it explains the context while keeping that remaining work visible.
A list locates services without certifying actions in another system
Subscriptions can be filtered by status and item type. That helps locate those containing external identifiers or lines and examine their commercial conditions. An item-type filter finds subscriptions containing at least one item of that type. It does not turn every element they contain into an external service or become a view of the operator’s system.
Suppose you find a suspended subscription containing a phone line. That row can help direct a review of the service and its agreement, but does not independently establish that the operator has suspended the line. Establishing what happened requires the appropriate action’s reference. Seeing the subscription become active again likewise does not certify each external operation.
Identification remains important. In Customers, search can use personal, commercial and item information, including identifiers and numbers. This helps recover the context when the customer starts with a plate or a number they recognize. Finding a result does not replace checking that it is the service being discussed.
The uniqueness rule also has a specific scope: the same device, line or External id can belong to only one subscription that is not cancelled. It helps organize permitted associations. It does not establish that every amount is correct, that every description matches the agreement or that a commercial error has become impossible.
For example, an item associated only once might belong to a subscription whose price or period needs correcting. Uniqueness does not validate those terms. In the fictional six-item account, the rule does not turn six items into three vehicles for charging purposes either. These are separate questions: where an item is associated and how the service price is applied.
The same case reveals another limit. Suppose the External id is accidentally left out: five items would remain associated. None would be duplicated, yet five at USD 10 would produce USD 50 rather than the USD 60 for the six agreed units in this example. The uniqueness rule does not independently detect the missing service. Reviewing the quantity requires comparing the items with the commercial agreement as well as avoiding duplicates. This calculation retains the example’s fictional price and common period; it does not introduce an extra charge for a line already included in another fee.
You can follow an external action through your team’s usual working methods and the relevant notes. Another authorized colleague should be able to recognize what is confirmed, what remains outstanding and who can continue. My customers does not thereby create a connection to the other system or prove that a written task was completed. Clarity comes from information retaining its meaning.
Begin with a relationship that is difficult to explain today
A useful first account to examine is one where the customer asks about several services and your team has to reconstruct the agreement. Before adding information, try explaining what is charged, its period and where each part is administered. The uncertainties that emerge identify information to clarify, without making the first use an obligation to move your whole customer base.
That initial conversation can reveal the benefit you actually need. Perhaps the customer recognizes each vehicle but cannot identify the renewal. Perhaps your team knows the amount but not where a line must be managed. A clearer commercial record helps retain that context; it does not require claiming every related operation will become automatic.
The My customers guide explains access conditions. The main account can open the menu from fifty licensed devices, combining Standard and Professional; saving requires one hundred. Below one hundred, the section provides a preview without saving, and the free version is excluded. Subuser access depends on their type and privileges.
Preparation includes the communications and payment options you will actually offer. Each subscription has its payment link, with the service information and available gateways. The customer must complete the relevant payment process. Sharing the address does not establish an automatic recurring charge or activate third-party services.
For more detail about message wording or checking a transaction, continue with the articles on reminders and reviewing outstanding payments . The central decision here is maintaining one understandable explanation of mixed services while keeping their places of administration clear.
The cover and video illustrate that idea. They do not show actual customer accounts or an integration controlling every platform. To review your case, contact Plaspy with the services you charge for, their periods and where they are managed . That supports a discussion about a specific organization and the checks your team will still need to perform.
