External report for 1C Difference 2.2 for Kazakhstan

Automation of data processing Execution of calculations according to specified algorithms, Automatic document generation Integration with 1C There are input data in one table that need to be automatically transferred to another, calculations performed according to certain rules, and ready documents generated for further automatic loading into 1C

Attention Production is looking for a specialist for long-term cooperation!!! I am looking for a developer or a team that will help create an inexpensive, reliable, and easy-to-use production automation system for the chicken deboning workshop. The main goal is to maximize the automation of the weighing process, product labeling, inventory management, and ensure complete traceability of each batch of products from the receipt of raw materials to delivery to the customer. Main functionality 1. Integration with weighing equipment Connecting electronic scales to a personal computer. Automatic weight acquisition without manual input. Support for one or multiple workstations. 2. Automatic printing of thermal labels After weighing, the system automatically prints a label containing: product name; weight; batch number; production date; expiration date; code or full name of the employees who performed the operation; barcode or QR code; other necessary information according to the company's requirements. 3. Automatic inventory management The system must provide: receipt of carcasses for production; automatic write-off of raw materials; accounting of finished products; real-time inventory tracking; control of losses and product output. 4. Product shipment Formation of customer orders. Order picking. Automatic write-off of products from the warehouse. Control of inventory after shipment. 5. Traceability This is one of the most important modules of the system. It is necessary to ensure the ability to determine at any moment: from which batch of carcasses each unit of product was made; when it was produced; who specifically processed it; on which scales it was weighed; what weight indicators were recorded; when and to whom it was shipped. The system should also allow for quick retrieval of all units of product made from a specific batch of raw materials, which is especially important in case of inspections or product recalls. 6. Reports It is desirable to implement: inventory levels; product movement; employee productivity; output of products from each batch; losses during deboning; history of all operations; production statistics for any period. Preferences Simple and intuitive interface. Minimal manual data entry. Operation without expensive licenses. Local database with backup capability. Possibility of further functional expansion. Support for integration with scales and thermal printers (Zebra, Godex, TSC, Xprinter, or similar). In your response, please indicate Examples of similar projects. Proposed development technology. Estimated cost and completion time. Supported models of scales and thermal printers. Suggestions for system improvement. Prospects for cooperation In the future, there are plans to expand the system to a full-fledged production ERP with automation of all enterprise processes: procurement, inventory, production, quality control, logistics, sales, and financial accounting. Therefore, I am looking for a specialist or team for long-term cooperation. I would also immediately add another requirement that will significantly increase the practical value of the system: calculation of product output and losses. For example, if 1,000 kg of carcasses are received, the system automatically shows: how much fillet, thighs, wings, drumsticks, etc. were obtained; overall output percentage; technological losses; productivity of each employee or team; cost of each item.

Communication/recruitment agency. CRM — NetHunt (Business plan, 2 users). Two funnels — candidates and clients — have already been created independently. This is an internal working tool for a team of 2 people, not a public product. The goal is to correctly configure the system, automate routine tasks, and connect external tools (Google Form, Notion, Telegram) to the CRM. What needs to be done Review and optimize the structure of the database and two funnels (fields, stages) for recruitment processes. Automatic emails to candidates when moving between stages of the funnel (native NetHunt workflow + templates). Auto-creation of candidate cards from applications — evaluate two options: (a) native NetHunt form; (b) from the existing Google Form via webhook/Make. Notion → NetHunt: when creating a record in the database [SPECIFY WHICH], a card is automatically created in the CRM (via Make/Zapier, field mapping, duplicate protection). Connecting Telegram — evaluate two options: (a) two-way integration (candidate chats become cards, responses from CRM); (b) one-way auto-messages. Testing all scenarios + training 2 people + a short instruction. Criteria for successful results All automations work stably, without duplicates and data loss. The team understands how to use the system and make simple edits independently. There is a short, clear documentation on the setup. Please specify in your response Fixed price separately for each item + total. Deadline for completion. Whether support after launch is included (e.g., bug fixes for 1–2 weeks). Similar cases: implementation of NetHunt and/or integrations via Make.

We are looking for a specialist in Google Sheets to support the existing work tracking table and payroll calculation. The table has already been created and contains many formulas and interconnections between sheets. Currently, there are errors that need to be found and corrected. Requirements: analyze the structure of the table; find and fix errors in the formulas; restore the correct functioning of the table if necessary; explain the working principle so that we can independently make simple changes in the future; provide ongoing support for the table if possible. Experience with Google Apps Script will be an advantage if the table uses automation. Before starting work, I will provide access to the table and explain what the problem is.

Adding document photos via a Telegram bot. The connection to BAS should be implemented as an extension - without changing the configuration. Settings: 1. Log for setting which objects it will work with. An object can be a document or a directory. 2. User log of the bot. The log confirms bot users, links to BAS users (a bot user may not be a BAS user), default department 3. Access settings for storage on FTP 4. Settings for departments and directories on FTP for departments Registration 1. by phone number 2. Confirmation of registration in BAS (check the active box) Operating mode. Mode 1. 1. From the document, the "add photo" button is pressed. (the button for the user is pressed only once, and until the operation is completed in the bot, it is inactive for this or other documents) 2. The bot sends a message to the user "add a photo or document". 3. The user attaches a photo (one or several) and presses the "send" button in the bot (or cancel) 4. A message in Telegram about the success of the sending. 5. The photo is attached to the document in BAS. Mode 2. 1. Photos are added to the bot 1 or several 2. A "send" button appears (or cancel) 3. A message in Telegram about the success of the sending 4. File upload to the department's directory. The file name is formed as: 2026_06_24_Document_Telegramuser