Venezuela SMS Guide: Sender IDs, Privacy & Route Policy

At a glance

A quick operational read on Venezuela. Anything marked route-dependent is decided by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick.

SMS to mobile: Supported on selected contracted A2P routes
Number format: +58 followed by the ten national digits; the domestic trunk zero is removed when normalising to E.164
Country code and MCC: Country code 58, mobile country code 734, national significant number ten digits
Number validation: Confirm the destination is Venezuelan, messaging-capable mobile before sending
New mobile range: CONATEL introduced national destination code 422, assigned to Corporación Digitel, with effect from 7 February 2025
Standard consumer mobile ranges: National destination codes 412, 414, 416, 422, 424 and 426 carry standard consumer mobile numbers
Mobile satellite range: The 415 range is allocated to Globalstar mobile satellite service rather than to a terrestrial mobile network
415 handling: Validate 415 destinations separately; do not assume terrestrial A2P mobile delivery for them
Number portability: Twilio marks number portability as unavailable on its current Venezuela route
Portability re-check: No active nationwide portability service was identified in the sources reviewed; re-check before launch and before relying on any NDC or operator mapping
Visible sender presentation: Route-assigned, preserved or replaced according to the selected provider and operator path
Alphanumeric sender: On one major provider's current route, a registered alphanumeric sender is preserved only towards Digitel; other paths overwrite it
Sender rewriting: Unregistered senders can be replaced with a route-assigned or randomised number outside your control
International numeric sender: Not preserved and rewritten on Twilio's current Venezuela route
Domestic long code: Unsupported on Twilio's current Venezuela route
Dedicated or local short code: Operator-capable in Venezuela, but not offered by Twilio's current service
Sender confirmation: Confirm the actual visible sender, per operator path, before launch
Two-way SMS: One-way only on that provider's current Venezuela route; two-way SMS is not supported
Inbound programmes: Treat replies, STOP handling by reply and any inbound requirement as unavailable until explicitly confirmed and tested on the path you buy
Concatenation: Not supported on that provider's current Venezuela route
Message length: Design for a single segment; long copy can be truncated or split unpredictably where concatenation is unavailable
Unicode / UCS-2: Support varies by sender and operator path on that provider's route, and the Movistar path carries a risk of accented characters being flattened
Encoding validation: Test your real Spanish copy, and its real segment count, on the exact route before launch
MMS: That provider converts MMS into an SMS containing a URL
Constitutional privacy duties: Constitution articles 28, 48 and 60 cover access to and rectification of personal data, secrecy of private communications, and limits on the use of information technology
Consumer information: Constitution article 117 recognises a right to adequate and non-deceptive information about goods and services
Permission standard: Send promotional SMS only on prior express permission that is clear, specific, recorded and evidenceable
Opt-out standard: Offer a free and simple opt-out that does not depend on a reply
Suppression standard: Honour every opt-out with immediate suppression across every sending system and list
Contact timing standard: Send promotional traffic in recipient-local daytime hours as our own operating standard
Last reviewed: 1 August 2026

Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Venezuelan law. Two providers can behave differently on the same day and a route can change its policy without notice. Numbering, the 0422 range and the constitutional and telecommunications duties, by contrast, are regulation and apply to every route.

Law, route policy and recommendation

Venezuela is a clear example of why these three layers must stay separate. Most of the constraints teams hit in production are route policy, not statute, and most of the governance you should apply is our recommendation rather than a published national rule.

Law / regulation
Venezuelan law and regulation
CONATEL administers the national numbering plan for country code 58, including the ten-digit national significant number and the mobile ranges. The Organic Telecommunications Law is the governing statute for telecommunications activity. Constitution articles 28, 48 and 60 create data access and rectification rights, protect the secrecy of private communications and limit the use of information technology against honour, privacy and reputation, and article 117 recognises a consumer right to adequate and non-deceptive information. The Special Law against Computer Crimes penalises unlawful access to and misuse of data and systems.
Carrier or route policy
Supplier and carrier route policy
Whether your sender survives, whether a reply can reach you, whether a long message concatenates and whether accented characters render are decided by the supplier and operator path. On one major provider's current Venezuela route, two-way SMS and concatenation are not supported, MMS is converted into an SMS containing a URL, portability is not supported, a registered alphanumeric sender is preserved only towards Digitel, and other senders may be overwritten or randomised. Another supplier can differ on any of these on the same day.
Flowstates recommendation
Flowstates recommendation
The official sources reviewed for this guide did not reveal a comprehensive private-sector data-protection statute or a nationwide SMS-specific marketing-consent regime in force as of 1 August 2026, so the discipline has to come from you. We recommend running permission capture, identification, opt-out handling, suppression and retention to the same standard you would apply in a strictly regulated market, and treating every route behaviour as unproven until you have tested it on the exact path you buy.

Numbering and networks

Get the numbering right before you debug delivery. Most Venezuelan delivery tickets that look like carrier problems are malformed destinations or an assumption about the operator behind a prefix.

Law / regulationCountry code
Venezuela uses country code 58.
Law / regulationMobile country code
The mobile country code is 734.
Law / regulationNumber length
The national significant number is ten digits, excluding the country code.
Law / regulationNational prefix
The national (trunk) prefix is 0 and the international prefix is 00.
Law / regulationE.164 normalisation
Store destinations as +58 followed by the ten national digits, dropping the domestic trunk zero.
Law / regulationMobile ranges
Standard consumer mobile national destination codes are 412 and 422 for Digitel, 414 and 424 for Telcel (Movistar), and 416 and 426 for Movilnet.
Law / regulationNew 0422 range
CONATEL introduced national destination code 422, assigned to Corporación Digitel C.A., with an introduction date of 7 February 2025.
Law / regulationMobile satellite
The 415 range is allocated to Globalstar mobile satellite service rather than to a terrestrial mobile network.
Flowstates recommendation415 validation
Validate any 415 destination separately before including it in an A2P campaign, rather than assuming it behaves like a terrestrial mobile number.
Flowstates recommendationRange hygiene
Make sure your validation, routing tables and analytics recognise 0422 as a live mobile range. Older allow-lists built before February 2025 can reject those destinations outright.
Flowstates recommendationLine-type validation
Validate Venezuelan jurisdiction and messaging-capable mobile line type before sending, rather than filtering only on string length.
Carrier or route policyPortability
One major provider marks number portability as unavailable on its current Venezuela route, and no active nationwide portability service was identified in the sources reviewed. That is a provider route position plus an open question, not a statutory statement.
Flowstates recommendationPortability re-check
Re-check the portability position with your supplier before launch, and again if you build any routing logic that assumes a prefix maps permanently to one operator.
Flowstates recommendationOperator resolution
Because sender behaviour differs by operator path in Venezuela, resolve the destination network for your own routing and testing rather than assuming one behaviour across all three mobile networks.

E.164 example

+58 4XX XXX XXXX

A national form written as 0412 XXX XXXX becomes +58 412 XXX XXXX. Ten national digits after the country code, with the trunk zero removed.

SenderID options

Sender presentation in Venezuela is decided by the selected route and the destination network, not by a national sender register. Nothing below describes a universal Venezuelan sender behaviour: each row is the behaviour of a selected supplier path.

Carrier or route policy

Every field in this table is carrier or route behaviour on a selected supplier path, and it varies by supplier and by destination network. None of it is Venezuelan law, and none of it should be read as a general Venezuelan sender rule. Commercial and provisioning detail is handled privately during onboarding rather than published here.

Preregistered alphanumeric sender for Digitel

Best for: Brand-visible traffic to Digitel destinations on a selected provider path that supports sender preregistration
Recipient sees: On that selected registered Digitel path, the approved brand sender is preserved; no other Venezuelan operator path is covered by it
Replies: Not supported on that route

Dynamic alphanumeric sender

Best for: Not recommended; included because traffic often defaults into it when no preregistration exists
Recipient sees: The route may substitute a random or route-assigned short code, long code or generic alphanumeric sender. The submitted sender is not preserved.
Replies: Not supported on that route

International numeric sender

Best for: Traffic that must terminate where alphanumeric presentation is unavailable
Recipient sees: The route may substitute a random or route-assigned short code, long code or generic alphanumeric sender. The submitted sender is not preserved.
Replies: Not supported on that route

Dedicated or local short code

Best for: A selected programme that needs a stable domestic origin, where a contracted route offers one
Recipient sees: A short numeric origin tied to that selected programme. This is a selected programme and Twilio's current service does not offer it.
Replies: Route-dependent; treat as unavailable until confirmed

SenderID options
Option	Best for	Recipient sees	Replies
Preregistered alphanumeric sender for Digitel	Brand-visible traffic to Digitel destinations on a selected provider path that supports sender preregistration	On that selected registered Digitel path, the approved brand sender is preserved; no other Venezuelan operator path is covered by it	Not supported on that route
Dynamic alphanumeric sender	Not recommended; included because traffic often defaults into it when no preregistration exists	The route may substitute a random or route-assigned short code, long code or generic alphanumeric sender. The submitted sender is not preserved.	Not supported on that route
International numeric sender	Traffic that must terminate where alphanumeric presentation is unavailable	The route may substitute a random or route-assigned short code, long code or generic alphanumeric sender. The submitted sender is not preserved.	Not supported on that route
Dedicated or local short code	A selected programme that needs a stable domestic origin, where a contracted route offers one	A short numeric origin tied to that selected programme. This is a selected programme and Twilio's current service does not offer it.	Route-dependent; treat as unavailable until confirmed

Confirm the visible sender per operator path, and confirm the fallback behaviour when the primary route is unavailable, before you launch. A fallback route that silently randomises your sender will break OTP recognition and brand trust even when delivery reports look healthy.

What changes by traffic type

OTP, transactional and marketing traffic fail in different ways in Venezuela. Split them across routes, templates and permission records rather than running one blended stream.

OTP and authentication

Short-lived codes where a rewritten sender or a split message costs you conversions, not just deliveries.

Carrier or route policy
Concatenation is not supported on one major provider's current Venezuela route.
Flowstates recommendation
Where concatenation is unavailable on your contracted path, keep every OTP message inside a single segment.
Carrier or route policy
Two-way SMS is not supported on that provider's current Venezuela route.
Flowstates recommendation
Do not design an OTP flow that depends on the recipient replying.
Carrier or route policy
Sender presentation differs by operator path, so the same OTP can arrive from a brand name on one network and from a randomised number on another.
Flowstates recommendation
Put the code early in the message and keep promotional content out of it.
Flowstates recommendation
Do not put a link in an OTP message.
Flowstates recommendation
Give the user a non-SMS fallback such as voice, email or an in-app path, because a rewritten sender can suppress recognition even when the message arrives.
Flowstates recommendation
Measure OTP conversion per operator path rather than in aggregate, so a single-network sender problem is visible early.

Transactional and service

Messages the recipient expects because of something they already did with you.

Flowstates recommendation
Keep transactional templates separate from marketing templates and from the routes that carry them.
Carrier or route policy
MMS is converted into an SMS containing a URL on that provider's current Venezuela route.
Flowstates recommendation
Do not design image-led service notifications for Venezuela; assume text and a link.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners so the link matches the brand in the message body.
Flowstates recommendation
Do not attach promotional offers to a service message to avoid the discipline you would apply to marketing.
Law / regulation
Information you give consumers about the goods or services they hold should be adequate and non-deceptive, consistent with the consumer information right in Constitution article 117.

Marketing and promotional

Promotional traffic in a market where the sources reviewed did not reveal a nationwide SMS-specific marketing-consent regime or a national do-not-contact registry in force as of 1 August 2026, so your own controls are the control.

Law / regulation
Constitution articles 48 and 60 protect the secrecy of private communications and limit the use of information technology against honour, privacy and reputation, and they apply to promotional messaging like any other processing.
Flowstates recommendation
Hold a higher internal standard rather than a lower one: send promotional SMS only to recipients who gave you a clear, specific and recorded permission.
Flowstates recommendation
Identify the sending brand in the message body, because the visible sender may be rewritten by the route.
Carrier or route policy
Two-way SMS is not supported on that provider's current Venezuela route, so a reply-based STOP keyword cannot be relied on there.
Flowstates recommendation
Offer an opt-out route that does not depend on a reply, such as a link or an account setting.
Flowstates recommendation
Send promotional traffic in local daytime hours as our own operating standard, not as a published national rule.
Flowstates recommendation
Suppress opt-outs immediately across every sending system, including campaign tools and CRM.
Flowstates recommendation
Do not use purchased or rented lists.
Flowstates recommendation
Take Venezuelan legal advice on your specific marketing programme rather than inferring a permitted contact window or frequency from another market.

Venezuela privacy, data-governance and marketing position

Venezuela separates questions that are usually bundled together elsewhere. There is a strong constitutional privacy layer, a telecommunications statute and a computer-crime statute. Alongside those, and as a neutral description of the landscape rather than a rule you can rely on: the official sources reviewed for this guide did not reveal a comprehensive private-sector data-protection statute or a nationwide SMS-specific marketing-consent regime in force as of 1 August 2026. That is an open landscape, not a permission, and it changes which of your controls are legal duties and which are your own standard.

Law / regulation
Constitution article 28 gives every person the right to access the information and data held about them in official or private registries, to know the use and purpose of that data, and to ask a competent court to update, rectify or destroy it where it is wrong or unlawfully affects their rights.
Law / regulation
Constitution article 48 guarantees the secrecy and inviolability of private communications in all their forms.
Law / regulation
Constitution article 60 protects honour, private life, intimacy, self-image, confidentiality and reputation, and provides that the law shall limit the use of information technology to safeguard those rights.
Law / regulation
Constitution article 117 recognises the right of every person to adequate and non-deceptive information about the goods and services they consume.
Law / regulation
The Organic Telecommunications Law is the governing statute for telecommunications activity in Venezuela and places CONATEL as the national regulator.
Law / regulation
Article 12 of the Organic Telecommunications Law sets out users' rights in the telecommunications context, including respect for privacy, the inviolability and secrecy of their communications, and protection against the improper use of their personal data. It is a users' rights provision, not an SMS marketing-consent statute.
Law / regulation
Articles 20, 21 and 22 of the Special Law against Computer Crimes penalise the improper obtaining, disclosure or use of personal data and information held in systems, and the violation of privacy through images or communications. They govern how recipient data is handled, and they do not create a consent standard for commercial SMS.
Flowstates recommendation
Do not read the absence of a general data-protection statute as permission. The constitutional protections are real, courts can be asked to act on them, and a data incident involving Venezuelan recipients can also engage the computer-crimes statute.
Flowstates recommendation
Set your own consent standard and hold it: a clear, specific, recorded permission for marketing, captured at a point the recipient can recognise.
Flowstates recommendation
Record recipient, timestamp, source, notice version, purpose, channel and the wording shown at capture, so you can evidence permission if it is ever challenged.
Flowstates recommendation
Identify the sending brand in the message body rather than relying on sender presentation.
Flowstates recommendation
Provide and honour an opt-out that does not depend on a reply, and suppress immediately across all sending systems.
Flowstates recommendation
Apply purpose limitation, retention limits and access controls to Venezuelan recipient data, and be ready to answer an article 28 style access or rectification request even though no sectoral procedure prescribes the format.
Flowstates recommendation
If your organisation is also subject to a data protection law elsewhere, apply that standard to Venezuelan traffic rather than dropping to the local floor.
Flowstates recommendation
Take Venezuelan legal advice before launching a promotional programme, and confirm the current position rather than relying on this page as the legal answer.
Carrier or route policy
Sender rewriting, the absence of two-way SMS, the absence of concatenation, UCS-2 handling, MMS conversion and portability support are route policy. None of them are Venezuelan law, and complying with one says nothing about the other.

Operational compliance checklist

The controls we expect to see before Venezuelan traffic goes into production, and the records we expect you to be able to produce afterwards.

Law / regulation
Store destinations as +58 followed by the ten national digits, removing the domestic trunk zero.
Law / regulation
Recognise 422 as a live Digitel mobile range introduced on 7 February 2025, alongside 412, 414, 424, 416 and 426.
Law / regulation
Do not treat the 415 range as terrestrial mobile; it is allocated to mobile satellite service.
Flowstates recommendation
Validate Venezuelan jurisdiction and messaging-capable mobile line type before sending.
Flowstates recommendation
Resolve the destination network for routing and testing, because sender behaviour differs per operator path.
Flowstates recommendation
Choose the sender deliberately: a preregistered alphanumeric sender where you have confirmed the selected path preserves it, or a validated numeric sender where you have not.
Flowstates recommendation
Confirm the live visible sender and the fallback behaviour on the contracted route, per operator path, before launch.
Flowstates recommendation
Design every message for a single segment where concatenation is unsupported, and verify the real segment count.
Flowstates recommendation
Do not build any flow that depends on the recipient replying while two-way SMS is unavailable on your route.
Flowstates recommendation
Keep OTP, service and marketing purposes, templates and permission records separate.
Flowstates recommendation
Record recipient, timestamp, source, notice version, purpose, channel and permission evidence as our evidence standard.
Flowstates recommendation
Identify the sending brand inside the message body.
Flowstates recommendation
Offer a non-reply opt-out in promotional messages and suppress immediately across every sending system.
Flowstates recommendation
Do not use purchased or rented lists.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners.
Flowstates recommendation
Test Digitel, Movistar and Movilnet paths before scaling.
Flowstates recommendation
Test sender preservation and replacement, Unicode and UCS-2 handling, message length behaviour and MMS conversion on the exact contracted route.
Flowstates recommendation
Apply purpose limitation, retention limits and access control to Venezuelan recipient data, and keep an internal process for access and rectification requests.
Flowstates recommendation
Keep evidence of templates, notices, permission, route approval, opt-outs and suppression.
Flowstates recommendation
Get Venezuelan legal review for marketing programmes, contact timing and any data-handling question this page marks as unsettled.

Encoding and delivery

Segment maths, Spanish-language traps and what to test on the real route before launch.

GSM-7 single segment: Typically 160 characters
GSM-7 concatenated: Typically 153 characters per segment
Unicode / UCS-2 single segment: Typically 70 characters
Unicode / UCS-2 concatenated: Typically 67 characters per segment
E.164 example: +58 4XX XXX XXXX

Carrier or route policy
Concatenation is not supported on one major provider's current Venezuela route, so the concatenated figures above may simply not apply to your path.
Flowstates recommendation
Where concatenation is unavailable, design to a single segment. Do not rely on a long message being split cleanly.
Flowstates recommendation
Spanish copy does not automatically force UCS-2. ñ, ¿, ¡ and é are in the basic GSM-7 alphabet, but á, í, ó, ú, curly quotation marks and emoji can force UCS-2 if you do not substitute them.
Carrier or route policy
UCS-2 support varies by operator path on that provider's Venezuela route, and some paths may flatten accented characters rather than render them.
Flowstates recommendation
Test your real Spanish copy, and its real segment count, on the exact sender and operator paths you will use.
Flowstates recommendation
Keep OTP messages in a single segment wherever practical. Do not treat a provider's maximum segment count as a copywriting target.
Carrier or route policy
MMS is converted into an SMS containing a URL on that provider's route.
Law / regulation
Remove the domestic trunk zero when normalising a national 04XX XXX XXXX form to +58 plus ten digits.

A country guide is only useful when the route follows it.

Country rules only help if the route your traffic actually takes respects them. That is the part we operate.

Per-country and per-category routing
Multi-vendor routing decided per country and per traffic category, so OTP, service and marketing traffic into Venezuela do not share one compromise route.
SenderID management
We manage sender presentation per route, per category and per operator path, including registered alphanumeric senders towards Digitel, and we check what the recipient actually sees before launch.
Carrier-grade failover
Automatic failover between vendors, with fallback senders that are themselves valid for Venezuela rather than a route that quietly randomises your sender.
Per-route visibility
Delivery, latency and OTP-conversion visibility per route, so a quality change on one Venezuelan operator path is visible while it is still small.
24/7 vendor escalation
We chase the vendor. Escalation runs around the clock rather than waiting for a support queue in another time zone.
BYOV / BYOG
Bring your own vendors or gateway and keep your commercial relationships while we operate the routing, sender policy and monitoring.
Branded short links
Branded short domains instead of public shorteners, so Venezuelan recipients see a link that matches the brand in the message body.

Developer docs Branded short links

What we need to validate your Venezuela route

Send us these and we can tell you what your Venezuelan traffic will actually do, per operator path, before you commit to a launch date.

Traffic categories in scope: OTP, transactional, marketing
Monthly volume by category and expected peaks
Sender presentation you want, and whether a registered alphanumeric sender towards Digitel is required
Sample message templates in the real Spanish copy you will send
Whether any message exceeds a single segment
Opt-in or permission journey, supporting evidence and the exact disclosure wording
Privacy notice and terms URLs
Internal objection, opt-out and suppression process, and its owner
Owner of your Venezuelan legal review
Link domains you intend to use
Whether you need replies or two-way messaging
MMS, Unicode or accented-character requirements
How numbers are collected, normalised and validated, including 0422 handling
Target launch date

Validate my Venezuela route Book a messaging review

Sources and change control

Official Venezuelan sources and the ITU's published national numbering plan control the law and numbering statements. Provider sources describe only their own current route. Where a provider page conflicts with CONATEL, we follow CONATEL and say so.

Official numbering
ITU — Venezuela national numbering plan (notified by CONATEL)
The ITU country page for Venezuela's E.164 national numbering plan as notified by CONATEL. Controls the country code 58, national prefix 0, international prefix 00 and ten-digit national significant number statements on this page.
Official numbering
ITU/CONATEL — numbering plan detail (PDF)
The notified numbering detail behind the ranges quoted here: standard consumer mobile national destination codes 412 and 422 (Digitel), 414 and 424 (Telcel/Movistar), 416 and 426 (Movilnet), with 415 allocated to Globalstar mobile satellite service. Records national destination code 422 as assigned to Corporación Digitel C.A. with an introduction date of 7 February 2025.
Statute
Organic Telecommunications Law (WIPO Lex record)
The governing statute for telecommunications activity in Venezuela, establishing the regime CONATEL administers. Article 12 sets out users' rights including respect for privacy, the inviolability and secrecy of communications and protection against improper use of personal data. Cited for that framing; it does not set commercial SMS marketing rules.
Constitution
Constitution of the Bolivarian Republic of Venezuela — article 28
Right of access to information and data held about a person in official or private registries, to know its use and purpose, and to apply to a competent court for its update, rectification or destruction where it is erroneous or unlawfully affects the person's rights.
Constitution
Constitution — articles 48 and 60
Article 48 guarantees the secrecy and inviolability of private communications in all their forms. Article 60 protects honour, private life, intimacy, self-image, confidentiality and reputation, and provides that the law shall limit the use of information technology to safeguard those rights.
Constitution
Constitution — article 117
Recognises the right of every person to adequate and non-deceptive information about the goods and services they consume. Cited as the consumer-information framing for message content, not as a specific SMS rule.
Constitution
Constitution — full text
Consolidated text used to read articles 28, 48, 60 and 117 in context.
Statute
Special Law against Computer Crimes (WIPO Lex record)
Articles 20 to 22 penalise the improper obtaining, disclosure or use of personal data and information held in systems and the violation of privacy of communications. Relevant to how Venezuelan recipient data is stored, accessed and shared, and not a consent standard for commercial SMS.
Statute (public-sector scope)
Infogovernment Law (WIPO Lex document text)
Venezuela's infogovernment statute for the national public administration. Cited only to show its scope: it governs public-sector information technology and does not create private-sector A2P marketing or consent duties.
Commentary (not a legal source)
Espacio Público — commentary on data protection and the Constitutional Chamber
Civil-society commentary consulted for context on how data protection has been read in Venezuela. Labelled commentary: nothing on this page relies on it for a legal statement.
Provider route policy
Twilio — Venezuela SMS guidelines
Describes its own Venezuela route: two-way SMS not supported, concatenation not supported, number portability not supported, MMS converted into an SMS containing a URL, a registered alphanumeric sender preserved towards Digitel while other paths overwrite the sender with a route-assigned or randomised number, and UCS-2 support varying by operator path with some paths flattening accented characters. This is that supplier's current route position, not Venezuelan law.

Change log

1 August 2026 — Initial publication; added CONATEL's 0422 Digitel range, separated constitutional and data-governance safeguards from provider sender policy, and documented one-way, non-concatenated route behaviour.

Last reviewed 1 August 2026

Disclaimer

This page is operational guidance, not legal advice. Requirements vary by law, message purpose, sender, provider, carrier route, recipient context and customer setup, and they change. Flowstates confirms the live route with you during onboarding, and you should take your own Venezuelan legal advice on marketing and data-handling obligations.

Venezuela SMS guide

At a glance

Law, route policy and recommendation

Venezuelan law and regulation

Supplier and carrier route policy

Flowstates recommendation