LINE Integration System Cost
Reservations, Cards, Notifications
LINE integration costs for SMBs: notifications from several hundred thousand yen, reservations plus cards about 1-3M yen. Plan fees, upkeep, quote checks.
Developing a system that connects a LINE Official Account to your business operations typically costs from a few hundred thousand yen for notification-only integration, roughly 1 to 3 million yen for reservations plus membership cards, and 5 million yen or more when it ties into core business systems. Many companies, however, can get by with standard features or a monthly integration service, so judging whether custom development is needed drives the cost. This article is written for owners of small and midsize businesses and covers what LINE integration can do, cost ranges by approach, running costs, and what to confirm before ordering. All figures are general guidelines and vary with requirements and vendors.
What LINE integration can do
Most customers already use LINE every day, so they do not need to install a new app. Dedicated reservation or membership apps tend to lose users at the download step, whereas LINE only requires adding your account as a friend. Across industries, the common uses are as follows.
- Taking and changing reservations: customers pick a date and time in the chat screen, and changes and cancellations are handled in LINE as well
- Reminder notifications: automatic messages the day before or on the day, reducing no-shows
- Digital membership cards and points: displaying cards and awarding points in LINE instead of paper cards or a separate app
- Automated replies to inquiries: answering common questions automatically and reducing missed inquiries outside business hours
- Orders and applications: accepting pre-orders, quote requests, or document requests through forms in the chat
- Links to internal systems: tying LINE friend information to customer management, booking ledgers, or core systems to send tailored messages
Trying to realize all of these at once tends to inflate costs. A realistic approach is to decide the top priority first and expand step by step. For the reservation part, see reservation system development costs, and for membership cards and points, see store point card app development costs.
Three ways to do it: standard features, integration services, custom development
There are broadly three ways to integrate with LINE. Depending on how far your requirements are met, the cost can differ by an order of magnitude.
| Approach | Typical initial cost | Typical monthly cost | Best for |
|---|---|---|---|
| 1. LINE Official Account standard features only | 0 yen | 0 yen and up (plan fee only) | Small businesses fine with broadcasts, greeting messages, and simple auto-replies |
| 2. LINE integration service (monthly SaaS or add-on tool) | 0 to tens of thousands of yen | Thousands to tens of thousands of yen (plus plan fee) | Companies that want standard features such as reservations, step messages, and membership cards quickly |
| 3. Custom development (Messaging API, LIFF, LINE Mini App) | Hundreds of thousands to millions of yen | From tens of thousands of yen for maintenance and servers (plus plan fee) | Companies that need unique workflows or integration with internal systems |
Note: These are general guidelines and vary greatly with features and scale. Always compare quotes from multiple vendors.
Even the standard features alone include broadcasts to friends, greeting messages, keyword replies, and rich menus (the fixed menu at the bottom of the chat screen). Try what standard features can do first and fill only the gaps with option 2 or 3 to avoid waste.
What custom development actually builds
Custom development mainly uses three technologies. The Messaging API is the gateway for your systems to send messages to LINE and receive messages from friends. LIFF opens web pages inside LINE, such as reservation forms or membership card screens. A LINE Mini App offers an app-like experience inside LINE; it requires review by LY Corporation and involves more procedures than an ordinary web page.
Owners do not need to learn these, but the heart of the design is how to link a friend's LINE ID with your customer records. If that is designed poorly, problems such as being unable to send notifications later or duplicate registrations tend to appear.
Cost guidelines for custom development
Custom development cost depends on the number of features and how deeply the system connects to existing ones. The ranges below are commonly seen in the industry, and actual amounts vary with requirements.
| Example configuration | Cost guideline | Duration guideline | Main content |
|---|---|---|---|
| Notification integration only | Several hundred thousand to about 1 million yen | About 1 to 2 months | Notify existing reservations or orders through LINE |
| Reservations plus reminders | About 1 to 2.5 million yen | About 2 to 4 months | Booking form, booking ledger, automatic reminders, admin screen |
| Reservations plus membership card and points | About 1.5 to 3.5 million yen | About 3 to 5 months | Above plus card display, point awards, visit history |
| Integration with core systems, POS, payments | About 4 to 8 million yen, more for large scale | 5 months or more | Two-way integration with inventory, sales, accounting, payment systems |
| Converting to a LINE Mini App | Add several hundred thousand to about 1 million yen | Review period separate | Review handling and meeting specification requirements |
Note: These are guidelines and vary greatly with conditions. Align the assumptions behind each quote (target operations, number of users, systems to connect) before comparing.
For the overall way of thinking about cost, see system development cost guide, and for connecting with external systems, see system integration and API development costs.
Thinking about running costs
Besides development, there are monthly costs. They fall into three groups: LINE Official Account plan fees, operating costs such as servers, and maintenance fees.
LINE Official Account plan fees
LINE Official Accounts have three plans with different monthly fixed fees and free message allowances. The following (excluding tax) is from the official LY Corporation business page.
| Plan | Monthly fixed fee (excl. tax) | Free messages | Additional messages |
|---|---|---|---|
| Communication plan | 0 yen | 200 | Not available |
| Light plan | 5,000 yen | 5,000 | Not available |
| Standard plan | 15,000 yen | 30,000 | Pay-as-you-go (up to about 3 yen per message) |
Note: Additional-message pricing was revised on October 1, 2026. Check the official page for the latest unit price.
What matters here is that free messages are counted as recipients multiplied by sends. For example, with 1,000 friends and four broadcasts a month, you use 4,000 messages. Individual replies to friends' messages are not counted, but system-sent notifications such as booking confirmations and reminders count toward delivery. The more friends you have, the more messages you use, so limiting frequency and audience is essential. The detailed counting rules can change, so confirm the latest official information before adoption.
Server and maintenance costs
Custom development incurs server and database costs, typically a few thousand to tens of thousands of yen per month. Maintenance, covering incident response, keeping up with LINE specification changes, and minor fixes, is generally budgeted at tens of thousands of yen per month. Monthly integration services (option 2) have these included in the fee, which is why their initial cost is small. Comparing the five-year total makes mistakes less likely.
Where costs tend to balloon
- Packing in too many features at once: building reservations, cards, points, and payments together inflates cost and schedule. Start with reservations alone, for example
- Integration with existing systems: older systems may have no way to extract data, requiring separate modifications
- Adding payments: prepayment such as by card increases design and testing effort
- Multiple stores and staff: slot management and permissions per store complicate requirements
- Custom design work: requesting many original designs for rich menus and screens raises cost
- Migrating existing friend data: if you already have many friends, linking existing data takes extra work
What to confirm in quotes
For how to read quotes, see guide to reading development quotes. For LINE integration orders, confirm the following in particular.
- Who is the contract holder of the LINE Official Account (your company or the vendor)
- Whether you hold administrator rights over the Messaging API channel and settings
- Where friend IDs and customer data are stored, and how data is returned after the contract ends
- Scope and cost of responding to LINE specification changes
- What the monthly maintenance fee includes and excludes
- For Mini Apps, how rework is handled if review is not passed
Risks to be aware of
LINE is an external service, and some things cannot be changed to suit your convenience. The main points are as follows.
- Specification changes and price revisions: delivery pricing and feature conditions can be changed by LINE, and additional-message pricing has indeed been revised. Leave margin in your running-cost estimates
- Handling personal information: a LINE friend ID becomes personal information once linked to a name or phone number. Decide the purpose of use, storage location, and access rights in advance
- Account permissions and departing staff: if an official account is managed from one employee's personal LINE, it may become inoperable when they leave. Use multiple administrators and set a procedure for removing permissions
- Mini App review: review can take time, making the release date hard to predict. Allow margin before launch
- Risk of being blocked: sending too often leads friends to block you, and you lose the friends you worked to gather
Decision criteria: when a service is enough and when to build
Most small and midsize businesses can start with an integration service (option 2). Custom development is worth considering when several of the following conditions overlap.
| Viewpoint | An integration service is enough | Consider custom development |
|---|---|---|
| Workflow | Standard flow common in the industry | Unique pricing calculation or booking rules |
| Internal systems | No integration needed, or CSV level | Automatic integration with core systems or POS is required |
| Scale | Up to a few thousand friends | Tens of thousands, or multiple sites |
| Timing | Want to start right away | Can take several months |
| Budget | Thousands to tens of thousands of yen a month | Can invest 1 million yen or more up front |
| Data handling | Fine to entrust to the service provider | Need strict management on your own servers |
For high-frequency retail that wants to run promotions and points together, DX for local retail stores is a useful reference. In every case, using option 2 for a few months first and identifying what is truly missing leads to firmer requirements and less wasted cost before moving to custom development.
Pre-order checklist
- You can state in one sentence the problem LINE integration should solve (fewer booking calls, more repeat visits, etc.)
- You have narrowed the top priority to one or two features
- You have confirmed standard features and monthly services are not enough
- You have decided who holds the LINE Official Account contract and who administers it (not dependent on one person's account)
- You have estimated monthly message volume and plan fee from friend count and send frequency
- You have checked how data can be extracted from the internal systems you want to connect
- You have decided the purpose of use and storage location for personal information
- You have obtained quotes from multiple vendors on the same assumptions
- You have confirmed what maintenance includes and how LINE specification changes are handled
- You have confirmed that data will be returned when the contract ends
Frequently asked questions
What is the minimum cost to develop a LINE integration system?
A small integration that only sends notifications from an existing system through LINE can sometimes start from a few hundred thousand yen. Including reservations and membership cards generally exceeds 1 million yen. Both are guidelines and depend on requirements.
What is the difference between a LINE Mini App and an ordinary LIFF app?
Both are web-based screens running inside LINE, but a Mini App requires review by LY Corporation and can offer an experience integrated with LINE features. An ordinary LIFF app needs no review but has limits on presentation and navigation. Choose according to your purpose.
Does the monthly fee rise as friends increase?
The monthly fixed fee is set by the plan and does not change with the number of friends. However, more friends means more messages, and beyond the free allowance the Standard plan incurs pay-as-you-go charges. Plans such as Light cannot send additional messages beyond the limit.
Is it safe to let the developer operate our LINE Official Account?
Entrusting it is possible, but we recommend that your company be the contract holder and also hold administrator rights. If it is in the vendor's name, you may be unable to take over the account and friend data when the contract ends.
If we want to start small, where should we begin?
Try your top-priority feature for a few months using standard features and a monthly integration service. Once the gaps in that operation are clear, requirements for custom development are easier to settle.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us