Open Company Data in North Macedonia: Official Sources, APIs and Reuse Rights

North Macedonia has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate North Macedonia is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is the Central Registry of the Republic of North Macedonia, CRM open-data and service pages, procurement, official statistics, tax, IP, securities-regulator and privacy/terms sources as separate layers. That makes North Macedonia a Central-Registry-led official source guide with CRM open-data, product/service, beneficial-owner privacy, controlled-access and no-unrestricted-bulk caveats, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in North Macedonia, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

North Macedonia is publishable as a deep refresh because the Central Registry is a strong legal-entity authority, CRM has stable English-language register, open-data, service, terms and privacy pages, and the country adds procurement, statistics, tax, industrial-property and securities-regulator context. The safe claim is not that North Macedonia exposes one unrestricted official bulk file for every company. The safe claim is that it has a practical official source stack where public pages, CRM products, web-service routes, open-data files and privacy-sensitive beneficial-owner records must be treated separately.

For practical work, the most useful source stack is: Central Registry of North Macedonia, CRM registers page, CRM open data, North Macedonia e-procurement, State Statistical Office, Public Revenue Office.

The safe editorial answer is this: North Macedonia has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious North Macedonia dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: the Central Registry of the Republic of North Macedonia, CRM open-data and service pages, procurement, official statistics, tax, IP, securities-regulator and privacy/terms sources as separate layers.
• Core source stack: Central Registry of North Macedonia, CRM registers page, CRM open data, North Macedonia e-procurement, State Statistical Office, Public Revenue Office.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in North Macedonia?

In North Macedonia, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, North Macedonia's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

publishable as a Central-Registry-led official source map with data.gov.mk, NBRM and gazette links held, and CRM terms, product, privacy and no-unrestricted-bulk caveats

Coverage, Access and Update Risk

The most common mistake in North Macedonia company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for North Macedonia

Controlled Access, CRM Services and Privacy Clearance

North Macedonia passes the refresh bar after holding unstable open-data, NBRM and gazette URLs from the public source matrix. CRM remains the official backbone, but CRM public pages, open-data files, product/service routes, web-service access and beneficial-owner records need separate reuse decisions.

Claims allowed in this article

• The Central Registry is the main official route for North Macedonia legal-entity and annual-account registry context.
• CRM open-data pages can support a careful API/open-data discussion.
• Procurement, statistics, tax and IP sources enrich company profiles but do not replace the Central Registry.

Claims blocked from this article

• Do not claim one unrestricted official bulk file for every North Macedonia company without checking CRM dataset and product terms.
• Do not link the held open-data portal or NBRM pages publicly until they pass live QA from the publication node.
• Do not treat registry or tax fields as marketing-contact permission.

Held source-risk findings

• North Macedonia open-data portal: data.gov.mk – held from public article because live QA timed out from this node.
• National Bank of North Macedonia: www.nbrm.mk – held from public article because live QA returned 403 from this node.
• Official Gazette of North Macedonia: slvesnik.com.mk – held from public source links because live QA returned TLS certificate verification failure from this node.

Source-risk notes

• CRM access boundary: public pages, open-data files, account services, web-service routes and paper outputs can carry different rules.
• Terms boundary: CRM website terms restrict reproduction, distribution, transmission and resale without approval.
• Beneficial-owner boundary: beneficial-owner products are compliance context and may include natural-person data.
• Open-data boundary: CRM open data supports a careful open-data discussion, but every dataset still needs field, licence and update checks.
• Language boundary: Macedonian, Albanian and English labels, legal forms and transliterations need normalization.

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Main Official Sources: Deep Dive

1. Central Registry of North Macedonia

Owner: official registry. Access: https://www.crm.com.mk/en.

• What it gives: Core legal-entity and registry-service context.
• Reuse value: CRM terms
• Main limitation: Registry products and detailed extracts may be controlled.

Central Registry of North Macedonia is a official registry source for North Macedonia. Its main practical value is Core legal-entity and registry-service context. Access is through https://www.crm.com.mk/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CRM terms. The main limitation is Registry products and detailed extracts may be controlled. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. CRM registers page

Owner: official registry. Access: https://www.crm.com.mk/en/about-crrnm/basic-institutional-data/registers.

• What it gives: Scope of Central Registry registers and annual accounts.
• Reuse value: CRM terms
• Main limitation: Overview page, not a bulk endpoint.

CRM registers page is a official registry source for North Macedonia. Its main practical value is Scope of Central Registry registers and annual accounts. Access is through https://www.crm.com.mk/en/about-crrnm/basic-institutional-data/registers, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CRM terms. The main limitation is Overview page, not a bulk endpoint. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. CRM open data

Owner: official registry/open data. Access: https://www.crm.com.mk/en/open-data.

• What it gives: Open-data evidence for Central Registry datasets.
• Reuse value: CRM open-data terms
• Main limitation: Dataset scope and update cadence must be checked.

CRM open data is a official registry/open data source for North Macedonia. Its main practical value is Open-data evidence for Central Registry datasets. Access is through https://www.crm.com.mk/en/open-data, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CRM open-data terms. The main limitation is Dataset scope and update cadence must be checked. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. North Macedonia e-procurement

Owner: official procurement. Access: https://e-nabavki.gov.mk/PublicAccess/home.aspx#/home.

• What it gives: Tender and supplier enrichment.
• Reuse value: procurement portal terms
• Main limitation: Procurement subset only.

North Macedonia e-procurement is a official procurement source for North Macedonia. Its main practical value is Tender and supplier enrichment. Access is through https://e-nabavki.gov.mk/PublicAccess/home.aspx#/home, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: procurement portal terms. The main limitation is Procurement subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. State Statistical Office

Owner: official statistics. Access: https://www.stat.gov.mk/Default_en.aspx.

• What it gives: Business-demography and macro context.
• Reuse value: SSO terms
• Main limitation: Aggregate/statistical layer.

State Statistical Office is a official statistics source for North Macedonia. Its main practical value is Business-demography and macro context. Access is through https://www.stat.gov.mk/Default_en.aspx, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: SSO terms. The main limitation is Aggregate/statistical layer. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. Public Revenue Office

Owner: official tax authority. Access: https://www.ujp.gov.mk/en.

• What it gives: Taxpayer and fiscal context.
• Reuse value: PRO terms
• Main limitation: Tax layer, not company master data.

Public Revenue Office is a official tax authority source for North Macedonia. Its main practical value is Taxpayer and fiscal context. Access is through https://www.ujp.gov.mk/en, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: PRO terms. The main limitation is Tax layer, not company master data. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. State Office of Industrial Property

Owner: official IP authority. Access: https://ippo.gov.mk/EN/Index_en.aspx.

• What it gives: IP-owner and trademark enrichment.
• Reuse value: SOIP terms
• Main limitation: IP layer only.

State Office of Industrial Property is a official IP authority source for North Macedonia. Its main practical value is IP-owner and trademark enrichment. Access is through https://ippo.gov.mk/EN/Index_en.aspx, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: SOIP terms. The main limitation is IP layer only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. SOIP about page

Owner: official IP authority. Access: https://ippo.gov.mk/EN/AboutSOIP.aspx.

• What it gives: Legal mandate and IP authority context.
• Reuse value: SOIP terms
• Main limitation: Mandate page, not searchable company data.

SOIP about page is a official IP authority source for North Macedonia. Its main practical value is Legal mandate and IP authority context. Access is through https://ippo.gov.mk/EN/AboutSOIP.aspx, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: SOIP terms. The main limitation is Mandate page, not searchable company data. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

9. CRM basic entity profile service

Owner: official registry. Access: https://www.crm.com.mk/en/services/obtain-information-or-confirmation-/other-services-certificates-and-data/basic-entity-profile-2191.

• What it gives: Shows which basic legal-entity fields can be requested from CRM.
• Reuse value: CRM terms; product and account rules apply
• Main limitation: Product/service route, not a blanket bulk licence.

CRM basic entity profile service is a official registry source for North Macedonia. Its main practical value is Shows which basic legal-entity fields can be requested from CRM. Access is through https://www.crm.com.mk/en/services/obtain-information-or-confirmation-/other-services-certificates-and-data/basic-entity-profile-2191, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CRM terms; product and account rules apply. The main limitation is Product/service route, not a blanket bulk licence. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

10. CRM beneficial-owner current status service

Owner: official registry. Access: https://www.crm.com.mk/en/services/obtain-information-or-confirmation-/business-data-and-registration-certificates/current-status-of-the-beneficial-owners-for-an-entity.

• What it gives: Beneficial-owner confirmation context for compliance-oriented datasets.
• Reuse value: CRM terms; privacy-sensitive compliance data
• Main limitation: Natural-person-adjacent data; not a marketing-contact source.

CRM beneficial-owner current status service is a official registry source for North Macedonia. Its main practical value is Beneficial-owner confirmation context for compliance-oriented datasets. Access is through https://www.crm.com.mk/en/services/obtain-information-or-confirmation-/business-data-and-registration-certificates/current-status-of-the-beneficial-owners-for-an-entity, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CRM terms; privacy-sensitive compliance data. The main limitation is Natural-person-adjacent data; not a marketing-contact source. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

How to Build a North Macedonia Company Dataset

A defensible North Macedonia company dataset should use CRM as the legal-identity anchor and preserve each official source as a separate evidence layer. The country is workable for company-data coverage, but not as a blind bulk-download workflow.

1. Registry seed: start with CRM register and open-data pages for legal identity, annual-account, business-entity and other-register context.
2. Product route check: separate free public pages, CRM basic-entity products, beneficial-owner outputs, distribution-system access, web-service access and paper delivery.
3. Reuse check: record CRM terms, dataset-level notes, authentication requirements and any approval requirement before redistribution.
4. Compliance check: use beneficial-owner, director, e-mail, address and document fields only with privacy and lawful-use review.
5. Dataset discovery: use CRM open data and State Statistical Office business demography for dataset/statistical context.
6. Activity enrichment: add procurement, tax, IP and securities-regulator context only where each source supports the field.
7. Commercial delivery: keep official company facts, compliance-sensitive fields and business-contact data in separate tables with separate controls.

Practical Options

Official open-data or API route

Start with the Central Registry and CRM register/open-data pages for legal-entity identity, annual-account and registry scope. Use CRM product pages for the actual information routes, CRM terms and privacy policy for reuse and personal-data boundaries, the Public Procurement Bureau and EPPS/e-marketplace pages for public-contract enrichment, the State Statistical Office for business-demography context, the Public Revenue Office for taxpayer/VAT context, SOIP for IP ownership and the Securities and Exchange Commission for listed/securities-market entities.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in North Macedonia, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

What Is Missing from Official Open Data?

• Do not claim that North Macedonia publishes one unrestricted official bulk company file for every company.
• CRM public pages, open-data files, account-based services, web-service routes and paper products can have different access rules.
• data.gov.mk is held from the public article because this node timed out during live QA.
• The National Bank public site is held from the source matrix because this node returned 403 on tested NBRM pages.
• The Official Gazette domain was checked but not used as a public linked source because live QA hit TLS verification failure from this node.
• Beneficial-owner, director, address, e-mail and document fields should be handled as compliance/privacy data, not outreach permission.
• Macedonian, Albanian and English labels, legal forms, transliteration and legacy country naming require normalization.
• Procurement, statistics, tax, IP and securities-regulator sources are enrichment layers, not replacements for CRM.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for North Macedonia should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For North Macedonia, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For North Macedonia, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for North Macedonia if you need a practical dataset rather than a list of source portals.

Commercial Dataset and Contact-Data Boundary

This North Macedonia guide supports CompaniesData’s company-database work, but official-source visibility is not marketing permission. CRM records, open-data files, procurement records, tax guidance, IP ownership and securities-regulator context can verify company facts. They do not automatically authorize email lists, phone outreach or sales-prospecting resale.

• Company identity layer: legal name, registration identifiers, legal form, status, jurisdiction, source URL and retrieval date.
• Official enrichment layer: procurement, statistics, tax, IP and securities-market context with field-level provenance.
• Compliance layer: beneficial-owner records, natural-person-adjacent data, CRM terms, authentication and web-service limits.
• Contact-data layer: business emails, phones, contact roles, segmentation and suppression require a separate lawful workflow through CompaniesData.cloud.
• Spanish-speaking buyers: Hispanic contact-data demand should be routed to CentraldeComunicacion.es instead of third-party contact-data competitors.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
Central Registry of North Macedonia	official registry	Core legal-entity and registry-service context.	CRM terms	Registry products and detailed extracts may be controlled.
CRM registers page	official registry	Scope of Central Registry registers and annual accounts.	CRM terms	Overview page, not a bulk endpoint.
CRM open data	official registry/open data	Open-data evidence for Central Registry datasets.	CRM open-data terms	Dataset scope and update cadence must be checked.
North Macedonia e-procurement	official procurement	Tender and supplier enrichment.	procurement portal terms	Procurement subset only.
State Statistical Office	official statistics	Business-demography and macro context.	SSO terms	Aggregate/statistical layer.
Public Revenue Office	official tax authority	Taxpayer and fiscal context.	PRO terms	Tax layer, not company master data.
State Office of Industrial Property	official IP authority	IP-owner and trademark enrichment.	SOIP terms	IP layer only.
SOIP about page	official IP authority	Legal mandate and IP authority context.	SOIP terms	Mandate page, not searchable company data.
CRM basic entity profile service	official registry	Shows which basic legal-entity fields can be requested from CRM.	CRM terms; product and account rules apply	Product/service route, not a blanket bulk licence.
CRM beneficial-owner current status service	official registry	Beneficial-owner confirmation context for compliance-oriented datasets.	CRM terms; privacy-sensitive compliance data	Natural-person-adjacent data; not a marketing-contact source.
CRM terms and conditions	official registry	Reuse, resale and website-use boundaries for CRM content.	CRM website terms; no reproduction/resale without approval	General website terms; dataset/product terms still need source-level review.
CRM privacy policy	official registry	Personal-data processing, authentication and anti-abuse context.	personal-data caution	Privacy policy, not a data source for commercial outreach.
CRM mission and institutional mandate	official registry	Authority and legal-entity information-base context.	CRM terms	Mandate context, not field-level data.
State Statistical Office business demography	official statistics	Business-demography trend and entity-population context.	SSO terms	Aggregate statistical layer, not legal company profiles.
Public Revenue Office VAT taxpayer guidance	official tax authority	VAT/taxpayer status context and fiscal interpretation.	PRO terms	Tax guidance, not registry master data.
Public Procurement Bureau	official procurement	Procurement authority and policy context.	BJN portal terms	Procurement layer only.
e-Pazar public procurement marketplace	official procurement	Small-value procurement, catalog and contract-enrichment context.	portal terms	Procurement subset; JavaScript application.
Securities and Exchange Commission	official regulator	Listed/securities-market entity and issuer context.	SEC terms	Sector-specific regulator layer only.

North Macedonia has a strong Central Registry source stack and a clean CRM open-data page, plus procurement, statistics, tax and IP authority pages. data.gov.mk timed out and National Bank pages returned 403 from this node, so those should be held or replaced before publication.

FAQ

Is there a single free official bulk company database for North Macedonia?

Not always. North Macedonia has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for North Macedonia company data?

The best first source is the Central Registry of the Republic of North Macedonia, CRM open-data and service pages, procurement, official statistics, tax, IP, securities-regulator and privacy/terms sources as separate layers. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting North Macedonia sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should North Macedonia company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Sources

• Central Registry of North Macedonia – official registry
• CRM registers page – official registry
• CRM open data – official registry/open data
• North Macedonia e-procurement – official procurement
• State Statistical Office – official statistics
• Public Revenue Office – official tax authority
• State Office of Industrial Property – official IP authority
• SOIP about page – official IP authority
• CRM basic entity profile service – official registry
• CRM beneficial-owner current status service – official registry
• CRM terms and conditions – official registry
• CRM privacy policy – official registry
• CRM mission and institutional mandate – official registry
• State Statistical Office business demography – official statistics
• Public Revenue Office VAT taxpayer guidance – official tax authority
• Public Procurement Bureau – official procurement
• e-Pazar public procurement marketplace – official procurement
• Securities and Exchange Commission – official regulator