Catalogue accuracy
Check attributes, product variants, prices and stock display rules.
BIG FISH / 1C-Bitrix support
1C-Bitrix website maintenance
Maintain 1C-Bitrix catalogues, orders, components and exchange with 1C. Improve the interface and verify data on both sides of the integration.
One-off or ongoing · scoped around your project
SKU-042 / availability
Stock in 1C
01Stock in 1C
02Exchange packet
03Product page
Fictional data. No production systems are connected.
SUPPORT × DESIGN × DEVELOPMENT
A familiar team.
The next stage of your product.
Exchange control
Distinguish successful file transfer from successful application of its data.
Interface development
Extend components and templates while keeping the system maintainable.
EXPLORE THE JOURNEY
From back-office data
to the product page.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / 1C-Bitrix support
Source
Stock changes in the accounting system. Identify the product and the owner of that value.
How the work is estimated ↘SKU-042 / availability
Stock in 1C
01Stock in 1C
02Exchange packet
03Product page
Fictional data. No production systems are connected.
02 / 1C-Bitrix support
Exchange
Check the transfer log, variant mapping and repeated packet handling.
How the work is estimated ↘SKU-042 / availability
Exchange packet
✓Stock in 1C
02Exchange packet
03Product page
Fictional data. No production systems are connected.
Check passed. The next stage can be approved.
03 / 1C-Bitrix support
Storefront
Verify the product page and basket after refreshing the relevant cache.
How the work is estimated ↘SKU-042 / availability
Product page
✓Stock in 1C
✓Exchange packet
03Product page
Fictional data. No production systems are connected.
A CLEAR PROCESS
See the result.
At every stage.
- 01
Request and priority
Clarify the outcome, business impact and conditions.
- 02
Estimate and agreement
Agree scope, cost and acceptance criteria before starting.
- 03
Work and validation
Prepare changes on a copy and verify related journeys.
- 04
Release and report
Publish the agreed result and update documentation.
SCOPE AND PRICING
The support
your product needs.
Hour packages are available for ongoing support. Individual tasks receive a separate estimate. Hosting, licences, third-party services and urgent work terms are specified in the proposal; they are not automatically included.
1C-Bitrix supportOne-off or ongoing
A precise quote follows a discussion of your project.
DOCUMENTATION
Project knowledge.
Stays with you.
Document coverage follows the agreed task. Secrets are stored separately from shared instructions.
Project record
Environments, versions, services, owners and access-management rules.
Release procedure
Pre- and post-release checks, backup and recovery conditions.
Change log
What changed, when it was released and how to verify it.
Team instructions
Content editing and new features without editing source code.
IN DETAIL / 01
Catalogue and variants
Map information blocks, attributes and product variants to the back-office model. Distinguish a product page from a specific variant so its price and stock belong to the right item.
Record mapping rules before changing the exchange and test a small product set. A removed item, missing value and zero stock are different states requiring agreed storefront behaviour.
IN DETAIL / 02
Exchange with 1C
Check exchange direction, schedules, identifiers and logs. A successful request does not prove a price was applied: verify both stored data and the interface.
For orders, define status mapping and authoritative sources. A repeated packet should not duplicate an order. If exchange is interrupted, identify the last completed stage and how to resume safely.
IN DETAIL / 03
Components and updates
Separate project-specific changes from core and standard components. Review module dependencies and licence status before updates. Significant changes are tested on staging with the appropriate PHP and database configuration.
Check user groups, personal pricing and restricted sections. After release, verify the catalogue, login, forms and checkout. The test list follows the functions of the particular website.
IN DETAIL / 04
Cache and load
Caching accelerates reads but needs correct invalidation after changes. Locate stale values in data, a component, server cache or browser. Clearing everything is not a substitute for finding the cause.
Investigate expensive queries, filtering and background work. Agree the timing and monitoring of large exchanges. Documentation covers data owners, schedules, constraints and exchange recovery.
FAQ
Before we start.
Do you only support your own projects?
Our main approach is to continue developing products we built. Projects from other teams are reviewed first: code, access and risks determine whether ongoing support is feasible.
Do we need a monthly subscription?
No. Individual tasks can be agreed separately. Ongoing support suits a regular stream of changes and a planned backlog. Use and rollover of hours are defined in the contract.
How quickly will you fix an error?
We first identify impact and cause. Response times, working hours and urgent contact arrangements are agreed separately. Resolution time depends on the fault and external services.
What do we receive?
A verified outcome, change description and report for the agreed scope. New functionality comes with updated instructions. Documentation depends on the task.
BIG FISH / MAINTENANCE
Find the right solution
for your project.
NEXT STEP
Your product can do more.
Let’s keep it moving.
Tell us what you want to change or which problem to solve. We will start with the task and propose a suitable way to work.