Interpret BASE contract scope, buyer identity, value fields and execution dates to select a defensible Portuguese public-sector account.
Portugal's BASE contract records can help a supplier decide which public organisation deserves further account research. The useful result is a documented view of what that organisation bought, from whom and over what delivery period. It is not simply a list of organisations associated with a keyword. A contract for an adjacent service can reveal a buying relationship while still offering little evidence of demand for the supplier's own product.
Start with a narrow commercial question. A business offering equipment-maintenance software might want to know which authorities buy standalone software subscriptions and which obtain software within a broader managed service. Those routes imply different potential customers. In the first case the public authority may be the direct buyer; in the second the existing service contractor could be the more relevant commercial account. BASE can help distinguish them if the researcher reads the scope behind the record.
The regulation governing BASE identifies several separate kinds of public information: contract scope, CPV classification, the procedure's base price, contract price, relevant dates, duration, actual total price and modifications. It also provides for identifying buyers and successful suppliers. Those fields support different research questions. The current consolidated Portaria 318-B/2023, particularly articles 2–4, explains the portal's role and the categories of information it makes public.
For account selection, establish the contracting organisation before interpreting the amount. Similar organisation names can refer to distinct legal or administrative entities. Conversely, separate departments may purchase through one contracting organisation. Keep the buyer's identifier with its name in the research record. That allows later searches to follow the same account when a name is abbreviated, translated or rendered differently in an announcement.
Then read the object of the contract and any available supporting document. A classification is useful for finding potentially relevant material, but the scope determines whether it resembles the supplier's offer. A broad information-technology contract might include hardware, implementation, licences and support. Calling its entire value software demand would make the apparent opportunity much larger than the addressable work.
A procedure's base price and the price of the resulting contract are different measures. The actual total associated with execution is another measure again. Preserve each under its own label instead of exporting all available amounts into a single value column. Where a field is absent or unclear, retain that condition rather than replacing it with zero in a commercial model.
The official BASE API documentation makes this separation visible through its example response. It includes different fields for the base price, contract price and actual total, as well as dates for publication, signature, award decision and closing. The response is explicitly test data; its sample amounts are useful for understanding the schema, not evidence of a real purchase. The documentation also describes separate retrieval routes for contracts, announcements and modifications, with token-based access.
A researcher working manually can apply the same discipline without building an integration. Keep one row for each identifiable contract and connect the related notices or modifications to it. Our guide to deduplicating procurement notices and amendments explains the broader counting problem. For a Portuguese account study, the immediate benefit is avoiding a claim that one buying relationship represents several independent purchases.
A publication date tells the researcher when information became public. It does not necessarily identify when work started or when the customer will buy again. A useful timeline separates award decision, contract signature, start of performance and the recorded duration or end. Then it records any available amendment that changes the original interpretation.
If the contract includes renewal options, a duration field alone may be insufficient to establish the final service horizon. Read the terms that explain how the period operates and whether the available record reflects an exercised option. The supplier's research note can then distinguish a confirmed date from a planning assumption. This makes the account useful to a commercial team without pretending to know a future procurement timetable.
The practical question is when the supplier could contribute something relevant. A replacement service may need preparation before a current contract ends. A complementary tool could be sold to the incumbent during performance. A small company with limited sales capacity should not treat those two possibilities as the same opportunity simply because both are associated with the same public buyer.
Consider a hypothetical review of two public organisations. Organisation A has a €90,000 contract described as a three-year software subscription. Organisation B has a €600,000 facilities-management contract that includes an equipment register. The larger recorded amount does not establish that B is a better software prospect. Its software component might be supplied internally by the service contractor and represent only a small part of the overall obligation.
For A, the researcher would investigate the subscription's implementation scope, users, support and transition needs. Dividing €90,000 by three gives a €30,000 annual arithmetic average, but it does not establish equal annual payments. An initial implementation charge could change the recurring economics. The contract terms, rather than the division, should determine how the supplier describes the existing purchase.
For B, the more useful next step may be identifying the successful facilities contractor and the work it performs. If that business already operates a suitable equipment register, a replacement pitch may be weak. If the public contract requires a new reporting service that the supplier can support, a defined subcontract proposition may be worth examining. The record helps choose the next research question; it does not answer it automatically.
The account note should state why one route is being pursued. A concise conclusion might identify direct subscription replacement for A and a possible service-contractor partnership for B, with separate evidence needed for each. That is more actionable than ranking them solely by the size of the published contract.
Company announcements can explain strategic direction or the significance of a particular purchase. Our reporting on Portugal's additional ICEYE satellite contract provides an example of programme context that may lead a supplier toward more specific account research. The commercial work still requires identifying the actual purchasing relationship and the scope relevant to that supplier.
Avoid importing the full value of a prominent programme into a database of near-term supplier opportunities. A specialist might address a small support task, a later service requirement or a subcontract through an established participant. Those are potentially useful routes, but their scale and timing need their own evidence. Connecting a public record to a narrow proposition produces a better account than attaching a broad programme headline to a company name.
Save the record identifier, source address, retrieval date and the fields used in the conclusion. Record whether a statement came from a contract document, a published field or an analytical assumption. If the source later changes, a colleague can then determine whether the commercial conclusion needs revision without repeating the entire search.
Before moving an account into active pursuit, check for a later notice, amendment or replacement contract and revisit any inferred completion horizon. A small number of well-supported accounts can justify focused commercial work. The useful output from BASE is therefore a set of buying relationships with defensible next questions, each grounded in an identifiable transaction and a scope the supplier could realistically serve.
Current consolidated BASE regulation and official API documentation reviewed 6 September 2026. API example is explicitly test data; worked account comparison is hypothetical.
Suggest a correction