Frequently Asked Questions

Files delivered by FTP enter the same Vodlix transcoding pipeline as every other upload, so they are encoded, packaged and ready to publish with their processing state visible in the CMS.

No. FTP is a universally understood delivery route in the media industry, so distributors can deliver to your Vodlix platform with the tools and processes they already use.

Consistently, and it is worth agreeing the convention before the first delivery rather than after. A consistently named batch can be matched to metadata almost automatically. An inconsistent one becomes manual work that no feature can remove.

An ingest folder is a door into your platform and should be treated like one, with separate credentials per partner. That way access can be revoked for one relationship without disturbing any of the others.

The same range the platform accepts elsewhere, since everything joins one pipeline after ingest. In practice the constraint is what a distributor can produce rather than what the platform will take.

App stores require digital subscriptions sold inside their apps to use their own billing, so each offer must exist per route. Vodlix gateway level packages keep those versions coherent and in step.

No. However a subscriber paid, whether through your website, the App Store or Google Play, Vodlix holds a single view of what they are entitled to, so support and reporting are never split.

App store price tiers are fixed steps that include local tax and platform commission, so in app prices rarely match web prices exactly. The store price is set in each store against the product ID the package carries, while the web price is set on the package itself.

No. The goal is that a viewer is never surprised by what they are charged, not that the figures match exactly. Vodlix lets you be clear about the price on each route.

Yes. Vodlix lets you choose which payment gateways may sell each package, so a promotional plan can be web only while standard tiers are available through every store.

Generally not directly, because the store holds that billing relationship. The honest answer is to direct them to the store, and the useful thing is that the platform records which route the subscription came through so you know before the conversation starts.

No. However the payment was taken, the platform holds one view of who is entitled to what, so support and reporting are not split by route even though the money arrived through different providers.

Which packages need to exist in which stores, and accepting that the prices will differ. Working that out early is considerably cheaper than discovering it during an app review, which is when most operators meet this for the first time.

Vodlix geo fencing controls where each title, package or the whole platform can be streamed, by allowing or blocking specific countries based on the viewer's location at playback.

Geo fencing enforces your licensing agreements by blocking playback in territories where you do not hold the rights, so your distribution stays aligned with studio and distributor contracts.

No. Geo fencing in Vodlix is an allow or block list configured in the admin area in minutes. There is no technical setup, no third party service and no code required.

Films, sports rights, live events, exclusive releases and market specific libraries benefit most, because these are the assets where regional rights are most often restricted or sold separately.

Yes. Vodlix lets you publish selected titles per market based on demand, launch plans or licensing, so each regional audience sees the catalogue you intend for them.

Yes. Vodlix vouchers work as a full payment method. Viewers redeem a voucher code to unlock a subscription plan or a title, or to add wallet credit that pays for content, with no payment gateway involved in the transaction.

Yes. Vodlix vouchers can be redeemed for platform subscriptions as well as individual content, so gift recipients and prepaid customers can start a subscription without entering card details.