The Context
Sogiry exists because Lithuanian ecommerce teams have been forced to choose between tools that do not quite fit: manual spreadsheets that are too slow, or global platforms built for larger and cleaner markets.
The Gap
Most global pricing tools are designed around Amazon-style catalogs, standardized product identifiers, and large Western markets. In Lithuania, competitors are fragmented, product naming is inconsistent, and local stock or promotion context often changes the right pricing decision.
The Solution
We are building Sogiry as the local pricing intelligence and automation layer for Lithuanian retailers first, with Baltic expansion where it makes sense.
Ramūnas Sabalys
Founder
Ramūnas Sabalys is building Sogiry from Lithuania for ecommerce teams that need reliable local competitor data, clear pricing controls, and automation that can be introduced gradually instead of switched on blindly.
ramunas@sogiry.comCompany details
A Lithuanian company, reachable directly
Lithuanian ecommerce does not behave like Amazon
Pricing automation only works when the market data underneath it reflects how customers actually shop and compare in Lithuania.
What global tools often miss
Fragmented competitor set
Your real competitive set may include Lithuanian retailers, category specialists, local marketplaces, and regional chains, not only international giants.
Lithuanian catalog language
Product names mix Lithuanian terms, English model names, specs, bundles, and retailer-specific abbreviations.
Inconsistent product identifiers
EAN/GTIN data is not always complete or used consistently across Lithuanian stores, so identifier-only matching leaves gaps.
Local stock and promotions
Availability, delivery terms, installment offers, and short campaigns affect pricing decisions as much as the visible shelf price.
How Sogiry is built for it
Starts from Lithuania
Coverage and matching logic prioritize Lithuanian competitors and store behavior before expanding outward.
Combines multiple matching signals
Sogiry looks at titles, attributes, identifiers, images, availability, and market context instead of relying on one field.
Designed for pricing managers
The product focuses on clear market visibility and controllable repricing rules, not a black-box optimization promise.
Adds automation gradually
Teams can begin with monitoring, move to approval workflows, and only then turn on bounded automation.
Automation starts carefully, not blindly
Because Sogiry can connect to your ecommerce platform and affect live prices, onboarding is intentionally hands-on during beta. The goal is to earn trust in the data and rules before automation runs at scale.
Diegimo etapai
Start in monitoring mode
Use Sogiry first to see competitor prices, product matches, and price gaps without publishing changes to your store.
Approve before publishing
During a pilot, rules can run in review mode so your team sees suggested price changes before anything goes live.
Automate only inside guardrails
When automation is enabled, price floors, margin floors, category limits, competitor filters, and SKU-level exceptions keep rules bounded.
If a pricing rule needs attention
The process is designed to make pricing issues operationally clear: pause, inspect, adjust, and resume only when the rule is safe.
Pause automation for affected SKUs or categories while prices are reviewed.
Use the change history to see which rule changed which product and why.
Adjust margin floors, price floors, competitor filters, or approval thresholds before turning automation back on.
Keep a named Sogiry contact and customer-side owner for urgent pricing questions during the pilot.
Practical trust details
Sogiry handles your pricing data and store integrations, so we are completely explicit about what data we use, how we protect it, and how our support works.
Data we need
Catalog or feed data, product identifiers, current prices, availability, competitor matches, pricing rules, and the integration credentials required to connect your store.
Data we do not share
Your margins, catalog, pricing rules, and strategy are not sold, shared with other customers, or exposed externally as competitive intelligence.
Security posture
Store connections use authenticated APIs and encrypted transport. During onboarding we review required permissions, limit internal access, and keep operational logs for troubleshooting.
Support expectations
During beta, support is direct and hands-on. Setup, competitor mapping, rule review, and pricing incidents are handled with a named Sogiry contact.
For onboarding and normal support, use pagalba@sogiry.com. For pilot pricing incidents, the escalation path and expected response window are agreed before automation goes live.