Frequently asked questions

We build and maintain custom web data collection workflows. Common projects include competitor price monitoring, product and availability collection, marketplace monitoring and recurring data feeds for internal systems.

Our primary service is data collection and delivery. We provide structured data that clients analyse in their own tools, dashboards and systems.

No. GetParsing is a managed service. We assess sources, build the workflow, validate output and maintain the collection process.

We assess online retailers, marketplaces, directories, catalogues and other public web sources. Feasibility depends on the website, data type, access conditions, volume and required frequency.

Yes, JavaScript-rendered and interaction-dependent sources can be assessed.

We assess sites with sessions, regional flows, rate limits, challenge pages and anti-automation controls. We confirm feasibility only after technical review.

Our standard service focuses on publicly accessible information. Authenticated sources are considered only when the client has proper authorisation and the project is suitable.

Common fields include product names, identifiers, categories, prices, promotions, availability, attributes, seller data, ratings and publicly displayed listing information.

Common schedules are daily, several times per week or weekly. Higher-frequency collection is assessed individually.

Yes, subject to feasibility, data volume, source behaviour and commercial practicality.

Yes, when regional or store-level data is available and can be selected reliably.

Depending on the project, data may be delivered in CSV, XML, JSON or Excel.

Options may include secure cloud folders, browser download, WebDAV, API-based delivery or a custom agreed workflow.

Yes. Provide a sample file, database structure or API schema and we will assess the required mapping.

Incremental outputs may be possible when reliable change detection can be implemented. Otherwise, full snapshots are used.

We investigate collection failures and update the workflow when the change is within scope and remains technically practical.

No provider can guarantee that an external website will never change, block access or become unavailable. We design for reliability, monitor production and respond to recoverable issues.

Pricing depends on source complexity, volume, frequency, geographic coverage, fields, delivery method and maintenance risk.

A limited sample or technical proof may be offered after source review. The exact scope depends on the project.

Send source URLs, required fields, target markets, update frequency, estimated volume and preferred output.

There is no universal answer. It depends on the source, data type, access method, jurisdiction, contractual restrictions and intended use. Clients are responsible for confirming that their use is lawful.

Projects involving personal data require additional review and may not be accepted. Our standard focus is factual commercial and product information that is publicly accessible.

A representative source list, required fields, desired refresh schedule, and preferred output format are enough for an initial review.

Yes. The schema is agreed around your downstream use, subject to what the selected sources provide.

Monitoring signals are used to identify collection or parsing failures. The appropriate response depends on the source change and agreed project scope.

Projects are reviewed for source access, data sensitivity, and intended use. Requests may be declined when responsible collection requirements are not met.