ZATCA Compliant Salla WMS Integration

$1500-3000 USD

Posted 1 minute ago

•

Ends in 6 days

$1500-3000 USD

Paid on delivery

Warehouse management system with ZATCA Phase 2 invoicing for 2 Salla stores I need a warehouse management system (WMS) for one warehouse that takes orders from two Salla stores (retail and wholesale), plus phone and walk-in orders, tracks stock, and issues ZATCA Phase 2 simplified tax invoices for every order. HOW DATA COMES IN (FIRST RELEASE) • Salla orders: imported from Salla's orders export (Excel), at least daily. Re-importing the same file must never duplicate orders or deduct stock twice. • Salla products: imported from Salla's products export (Excel) to keep the product list and SKUs current. • Stock vouchers: inbound and outbound vouchers (سند وارد / سند صادر) imported from xls/xlsx files exported by our ERP. Inbound adds stock, outbound deducts, and a voucher already imported is refused. • Price list: the ERP's VAT-exclusive price list, imported from Excel, used to price phone and walk-in orders (price + 15% VAT). • A live Salla API/webhook link is a later phase. Please build the import as a separate layer so the API can replace it without reworking stock or invoicing. CORE FUNCTIONS • Stock ledger: every movement (receipt, sale, return, adjustment, kit assembly) recorded with user, time, reason and source document. Stock on hand is the sum of the ledger. • Orders: imported Salla orders and manually created phone/walk-in orders, with items selected by hand, on one screen. • Returns: barcode scan, item back to stock (or written off with a reason), and a credit note referencing the original invoice. • Kits: assembling a kit moves stock from its components; selling a kit deducts the right quantities. • Commissions: monthly commission per salesperson, from percentage tiers plus fixed amounts on selected products. The rules will be provided. • Reports: sales and VAT per period (matching invoices and credit notes), stock card per product, returns and shipping reports, Excel export. INVOICING (ZATCA PHASE 2, SIMPLIFIED B2C INVOICES) • Each sale gets exactly one tax invoice, from this system only. Salla's VAT setting stays off. • Salla prices include 15% VAT. The VAT is taken out of the amount actually paid AFTER discounts: taxable amount = amount paid ÷ 1.15. Taxable amount + VAT must always equal the amount paid. • Discounts (coupons and special offers), shipping and cash-on-delivery fees are handled correctly. Charges appear as their own lines, and the lines add up to the invoice total. • Money is computed in exact decimals, never floating point. Rounding is half-up to 2 places, once per document. • UBL 2.1 XML, cryptographic stamp (ECDSA + CSID), QR code with all 9 TLV tags, UUID, invoice counter and hash chain. The counter cannot be reset or run in parallel. • Simplified invoices and credit notes are reported to ZATCA within 24 hours. Failures are queued and retried, never dropped. • The issue date and time come from the server clock at the moment of issue, not from the Salla order date, and users can't change them. • Issued invoices can't be edited or deleted. Corrections are made only by credit or debit note. • Onboarding follows ZATCA's steps (OTP, compliance CSID, compliance checks, production CSID), tested in the simulation environment first. • A printed invoice layout will be provided as a reference. USERS AND INTERFACE • Three users: warehouse custodian, admin, owner. Login is required on every screen. Role-based permissions aren't needed in the first release, but the design should allow them to be added later. • Arabic interface first (right to left), usable on desktop browsers with a barcode scanner. • Audit log of who created, changed or cancelled what, and when. TECHNICAL AND OWNERSHIP • You propose the technology stack, with your reasons. • Source code, hosting, domain and ZATCA certificates sit in company-owned accounts. Signing keys are never in the code or repository. • Daily backups with a tested restore. A restored or test copy must not be able to issue live invoices. • One-time payment, no subscription for the system or the e-invoicing module. • Development uses ZATCA simulation credentials only. Production credentials are set up by us at go-live. MILESTONES AND ACCEPTANCE • Milestone 1 - Core: Excel imports, stock ledger, orders, returns, manual orders. - Accepted when test files import correctly, re-imports create no duplicates, duplicate vouchers are refused, and stock cards balance. • Milestone 2 - ZATCA: invoice XML, signing, QR, reporting, credit notes. - Accepted when ZATCA's compliance checks pass in the simulation environment for invoices and credit notes. - Test orders with a coupon, a special offer, shipping and a cash-on-delivery fee must all produce invoices where taxable amount + VAT = amount paid. • Milestone 3 - Handover: commissions, reports, deployment documentation, and a one-month parallel run against our current figures. PLEASE INCLUDE IN YOUR BID • ZATCA Phase 2 projects you've delivered, ideally one we can check. • Any Salla integration experience. • Your proposed stack. • A fixed price and timeline per milestone.

Project ID: 40813446

About the project

42 proposals

Open for bidding

Remote project

Active 5 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

42 freelancers are bidding on average $1,891 USD for this job

User Avatar
Flag of BANGLADESH

Hello Sir, Consider it as done. I will build the Arabic RTL WMS with PHP, MySQL, and a separate Excel import layer for Salla and ERP files. Exact-decimal calculations, stock-ledger idempotency, credit notes, audit logs, backups, and ZATCA simulation compliance will be handled as core requirements. Plan: 1. Core: imports, duplicate protection, stock ledger, orders, returns, and manual sales — $5,000, 5 weeks. 2. ZATCA: UBL XML, signing, QR TLV, counter/hash chain, reporting retries, and credit notes — $4,500, 4 weeks. 3. Handover: commissions, reports, deployment documentation, restore testing, and parallel run — $2,500, 3 weeks. I have extensive experience with PHP/MySQL applications, Excel data integration, inventory workflows, and API-ready architecture. The Salla connector will remain replaceable for the later API phase. Thanks.

User Avatar
Flag of PAKISTAN

I can build a single-warehouse system that keeps both Salla stores, manual sales, stock and ZATCA invoices consistent. The critical safeguards are preventing a repeated import from moving stock twice and ensuring every sale produces exactly one invoice. I propose a Laravel application with PostgreSQL for transactional stock and invoice records, a separate Excel import layer so Salla API/webhooks can be added later, and an Arabic RTL desktop interface built for barcode scanning. Imports will use store-specific order IDs and voucher IDs to detect duplicates. A stock ledger will record every movement, including returns and kit assembly. For invoicing, I’ll use decimal amounts, reconcile VAT-inclusive payments after discounts and charges, and serialize issuance so the UUID, counter and hash chain cannot race. Signed UBL invoices and credit notes will enter a durable reporting queue with retries and alerts. Production signing will be disabled in test and restored environments; keys will remain outside the code. I’ll validate the coupon, offer, shipping and COD cases in ZATCA simulation before handover. I’ve structured the work around your three acceptance milestones, including restore testing and the parallel run. I won’t claim past ZATCA or Salla deliveries without verifiable references. Could you share sample exports, commission rules and the printed invoice layout so I can confirm the milestone scope?

User Avatar
Flag of PAKISTAN

Hello, A production-ready WMS for two Salla stores, warehouse operations, and Excel-based ERP imports requires strong software architecture and reliable data handling. Live Experts LLC brings over a decade of technical delivery experience and hundreds of completed projects, with expertise in PHP, MySQL, Excel, and software development, well suited to building your Arabic-first business platform. I can develop the system around a dependable stock ledger, idempotent Excel imports, product and price synchronization, manual and Salla orders, returns, kits, commissions, audit logs, and operational reports. The architecture can keep the initial Excel import layer separate from future Salla API/webhook integration, while MySQL supports traceable inventory movements and document relationships. PHP and MySQL also provide a practical foundation for role-ready authentication, invoice records, reporting, and company-owned deployment. My team’s experience with cloud APIs, integrations, automation, dashboards, and production systems supports the reliability, maintainability, backups, and ownership requirements in your specification. I would be pleased to build this WMS as a secure, scalable foundation for your ZATCA invoicing and warehouse operations. Thanks!

User Avatar
Flag of PAKISTAN

Hi, I understand you need a WMS for one warehouse serving two Salla stores, phone orders, and walk-in sales, with safe Excel imports, stock ledger, returns, kits, commissions, reports, and ZATCA Phase 2 invoices. I will keep imports separate from the stock and invoicing layers so a later Salla API can be added without rebuilding the core. Using PHP and MySQL, I will build Arabic RTL screens, duplicate-safe imports, exact decimal calculations, invoice and credit-note controls, audit logs, queued ZATCA reporting, backups, and simulation testing. Android can be supported for barcode scanning if required. I will deliver Milestone 1 in 30 days, Milestone 2 in 30 days, and Milestone 3 in 15 days. Fixed price: $2,750. Source code and deployment will remain in your company accounts, with signing keys kept outside the repository. Can you share the sample Salla/ERP files and confirm whether barcode scanning must work through Android, desktop USB scanners, or both? Please share sample Salla and ERP Excel files, the commission rules, and the invoice print reference. Start chat and let’s discuss the workflow and acceptance tests.

User Avatar
Flag of INDONESIA

Hi there, Thank you for outlining your requirements in such detail. I have successfully delivered multiple ZATCA Phase 2 e-invoicing projects, including B2C simplified invoicing with full UBL 2.1 XML, QR coding, cryptographic stamping, and ZATCA reporting—one recent reference is a retail POS solution currently in production, which I can provide details for upon request. While I have not integrated with Salla directly, I have extensive experience building modular import layers for eCommerce platforms, ensuring seamless Excel-based workflows and future-proofing for API/webhook upgrades. Your focus on accurate stock control, robust duplicate prevention, and auditability aligns well with my approach. I recommend a PHP (Laravel) backend with MySQL for reliability and clear audit trails, combined with a Vue.js web interface—optimized for RTL Arabic and barcode use. This stack is proven for compliance, performance, and maintainability. All ZATCA security and compliance steps, including key management and simulation testing, would be handled per best practices, ensuring your data and processes are fully protected. I'm confident in delivering a maintainable, user-friendly WMS that meets your milestone and compliance requirements. I look forward to discussing your commission structure, reporting needs, and deployment preferences in more detail. Best Regards

User Avatar
Flag of PAKISTAN

Hi there, I build cross-platform mobile apps for iOS and Android, including PHP, Mobile App Development and Android. Recent work includes a React Native app with social login, location search and service packages. For "ZATCA Compliant Salla WMS Integration" I would keep one clean codebase that is fast and easy to maintain. How I would approach it: - Confirm the screens, user flows and the backend or APIs needed - Build in milestones with test builds you can try on your phone - Prepare the app for store submission at handover Do you already have designs for the screens, or should I help with the UI as well? Message me and I will share a similar app I delivered. Umair

User Avatar
Flag of SERBIA

Your requirements describe a strong, well-defined WMS foundation: reliable Excel imports, an auditable stock ledger, Salla order handling, returns, kits, commissions, and ZATCA Phase 2 compliance. I would structure the system with a modular import layer, so Salla Excel files can later be replaced by API/webhooks without changing inventory or invoicing logic. The core would use a transactional relational database with exact decimal arithmetic, immutable invoice records, serialized counters, hash chaining, audit trails, idempotent imports, and queued ZATCA reporting retries. The Arabic RTL interface would be optimized for desktop warehouse workflows and barcode scanning. I would also design deployment around company-owned hosting, protected signing keys, daily backups, tested restores, and safeguards preventing restored environments from issuing live invoices. Delivery would follow your three acceptance-based milestones: core WMS and imports; ZATCA XML, signing, QR, reporting, and credit notes in simulation; then commissions, reports, documentation, and the parallel run. Each milestone can include documented test evidence for duplicate prevention, stock balancing, invoice totals, and ZATCA compliance. I can provide a detailed stack recommendation, implementation plan, fixed milestone pricing, and relevant ZATCA/Salla project evidence during the technical discussion.

User Avatar
Flag of INDONESIA

IF YOU ARE NOT HAPPY YOU DON'T PAY! The two weak points here are re-imports and the invoice chain. Each Salla order line needs a stable key so importing the same file twice does nothing. The invoice counter and previous-invoice hash have to come from one locked database transaction so they can never run in parallel. I'd use NestJS/TypeScript with PostgreSQL and exact-decimal money handling. The signing key would load from the server environment, so a restored copy without that key can't sign live invoices. The Excel imports would sit behind one interface that the Salla webhook can replace later. I don't have a public ZATCA project you can check, so passing the simulation compliance checks in Milestone 2 would be my proof. Does Salla's orders export show coupon discounts per line or only as an order total? Send me a message and I'll explain exactly how I'd approach your project.

User Avatar
Flag of PAKISTAN

Greetings! I can build your WMS with ZATCA Phase 2 simplified invoicing for both Salla stores, importing orders, products, vouchers and price lists from Excel as a separate layer so re-imports never duplicate stock. It includes a full stock ledger, manual orders, returns with credit notes, kits, commissions and reports. Invoicing uses exact decimals, UBL 2.1 XML, ECDSA signing, 9-tag QR and hash chain, with simulation testing and milestone-based fixed pricing. Happy to share ZATCA projects and my stack. Thanks, Revival

User Avatar
Flag of MALAYSIA

ZATCA Phase 2 integration on top of Salla for two stores is the real challenge here, specifically generating compliant XML/UBL invoices with the cryptographic stamp and QR code, then syncing that with your warehouse stock movements so inventory stays accurate across both stores. I have built API integrations between Salla and external systems before and can start today. Budget and timeline above are starting points based on the post. Once we go through both store setups and ZATCA's exact requirements, those numbers may shift. Want me to send a quick scope doc so we can get moving?

User Avatar
Flag of UNITED STATES

Hi there, The core challenge is building an Arabic-first WMS that imports two Salla stores and ERP Excel files without duplicate stock movements, then produces legally consistent ZATCA Phase 2 invoices and credit notes. I have strong hands-on experience with Android App Development, MySQL, Software Development, and API Integration, including inventory workflows, transactional ledgers, Excel imports, barcode operations, and tax-document integrations. My approach would be to: * Review the required Salla exports, ERP XLS/XLSX samples, invoice reference, ZATCA simulation requirements, and hosting constraints. * Identify the root cause of duplicate imports and define immutable idempotency keys for orders and vouchers. * Implement a clean, maintainable solution using a secure web stack with MySQL, Arabic RTL support, a modular import layer, and a future-ready Salla API boundary. * Test edge cases, reliability, performance, security, and integration behavior, including VAT-inclusive discounts, shipping, COD, returns, kits, credits, retries, and restore isolation. * Deploy or integrate the fix without disrupting the existing system, with backups, documentation, and a one-month parallel run. Milestone pricing and timeline: Core WMS and imports , $1,200 / 24 days; ZATCA invoicing and reporting , $1,200 / 24 days; commissions, reports, deployment, and handover , $600 / 12 days. Total: $3,000 / 60 days. Exact-decimal calculations, a serialized invoice counter, hash-chain persist

User Avatar
Flag of INDIA

Hello, You need one Arabic-first WMS to reconcile stock and orders from two Salla stores, phone sales, and walk-ins, while issuing compliant ZATCA Phase 2 invoices. The tricky part is keeping imports idempotent while preserving a single, auditable stock ledger. Invoice totals also need exact decimal handling, with VAT and charges reconciling after discounts. I'd propose a PHP and MySQL backend, with a separate Excel-import layer and transactional ledger entries; decimal arithmetic and a serialized invoice counter can protect totals and ZATCA sequencing. I've built similar inventory workflows with SKU-based stock movements and document-linked records. Kindly help me confirm a few scope details: 1. Which Salla export formats and sample files can you provide for orders and products? 2. Do you have the ZATCA simulation credentials and the required certificate onboarding access? 3. Should commissions and reports be included in the first deployment or after the invoice acceptance milestone? I can map the milestone acceptance checks into the build plan and recommend the stack in detail once I see the sample files. I look forward to hearing from you. Kind regards, Neel

User Avatar
Flag of PAKISTAN

Hi, I’ve reviewed your ZATCA Compliant Salla WMS Integration and understand what you’re looking to achieve. I can help you handle the required work with a clean, reliable, and professional approach. I have experience with PHP, Mobile App Development, Excel, Android, Inventory Management, MySQL, Software Development, Data Integration, Database Management, API Integration and can work effectively with your existing setup, requirements, and workflow. I’ll focus on proper implementation, responsive functionality, attention to detail, and thorough testing to make sure everything works as expected. I’ll also make sure the completed work is aligned with your requirements rather than just providing a quick or temporary solution. I’m available to start immediately and can work according to your required timeline. Best regards, Khadija Tul Kubra

User Avatar
Flag of INDONESIA

your salla warehouse system needs a re-imported excel file to never double an order or deduct stock twice, and i'd build it that way my team built a time-tracking platform with invoicing, and a hospital platform with an arabic right-to-left interface i'll stay on it through the simulation checks and the parallel run, with bug fixes and support after handover could you share a sample salla orders export and one erp voucher file so i can see the real columns? happy to talk it through whenever suits you Sela

User Avatar
Flag of GERMANY

Hello, "ZATCA Compliant Salla WMS Integration" - the critical part is keeping stock, order totals and tax invoices consistent across two stores and manual sales, without duplicate imports or financial discrepancies. I'll build the WMS around a MySQL stock ledger and a PHP-based application, with Excel imports isolated from the inventory and invoicing logic so a future Salla API connection can replace them cleanly. I'll also use decimal arithmetic for every VAT calculation, enforce unique import references and a serialized invoice counter, and keep issued invoices immutable. From order import and warehouse movements through returns, credit notes, ZATCA reporting, commissions and final deployment, I'll handle the implementation and testing directly. ZATCA simulation acceptance will be a key milestone, not an assumption. For the first release, are you open to PHP and MySQL as the proposed stack, with the ZATCA integration validated against your simulation credentials before production onboarding? Looking forward to working with you. Beate

User Avatar
Flag of PAKISTAN

My software development experience since 2012, combined with payment method and logistics partner integrations, gives me a strong foundation for building the operational system behind your two Salla stores, warehouse, phone orders and walk-in sales. I can develop a structured WMS covering Excel imports, duplicate-safe order and voucher handling, product and price synchronization, stock-ledger movements, barcode-based returns, kits, commissions, reporting and Arabic RTL desktop use. My e-commerce background also aligns well with Salla order flows, VAT-inclusive pricing, discounts, shipping and COD charges. I will keep the import layer separate so a future Salla API/webhook can replace Excel without redesigning stock or invoicing, while ensuring company ownership of the source code, hosting and sensitive credentials. The ZATCA Phase 2 requirements will be treated as core accounting functionality: immutable invoices, credit notes, exact decimal calculations, UBL 2.1, QR/TLV data, UUIDs, counters, hash chaining, queued reporting and auditability. I would be pleased to build this as a reliable one-time-payment system and discuss the project further.

User Avatar
Flag of MOLDOVA, REPUBLIC OF

Hello. I understand the complexities of integrating a warehouse management system that aligns with ZATCA Phase 2 invoicing requirements, especially when dealing with multiple order sources like Salla and ensuring accurate stock tracking. One key aspect of this project is the need for seamless data importation while preventing duplicates, which is crucial for maintaining inventory integrity. My experience includes successfully implementing similar systems that required precise data handling and tax compliance. Focusing on the outcomes, this system will not only streamline order processing and invoicing but also enhance the accuracy of your stock management, ultimately leading to improved operational efficiency. To better understand your needs, could you share how you currently manage data imports and any specific challenges you face with your existing system? Thanks, Artiom.

User Avatar
Flag of PAKISTAN

Hello, Full-stack development, PHP, database management, Excel processing and API integration align directly with your WMS requirements, including separate import layers for Salla and ERP files. I can build a custom warehouse system that supports two Salla stores, phone and walk-in orders, stock vouchers, product and price-list imports, duplicate prevention, stock ledger tracking, returns, kits, commissions and Excel reporting. My software development and database skills support reliable order and inventory records, while API integration provides a sound foundation for the later Salla webhook phase without restructuring the core system. I can also develop the Arabic RTL browser interface, login and audit trail, with the architecture prepared for role-based permissions and company-owned hosting and source-code control. The ZATCA Phase 2 requirements will be treated as core accounting functionality: exact decimal calculations, invoice and credit-note integrity, UBL XML, QR/TLV data, UUIDs, counters, hash chaining, queued reporting and protected signing-key handling. I am ready to build this WMS as a secure, maintainable one-time development project and would be pleased to deliver a system tailored to your operations. Thanks!

User Avatar
Flag of PAKISTAN

A reliable WMS for two Salla stores requires strong data integrity across Excel imports, stock movements, orders and invoicing. My skills in PHP, MySQL, API Integration, Excel and software development align directly with building this type of business system, including a separate import layer that can later be replaced by a live Salla API without reworking stock or invoicing. I can coordinate the development of the Arabic RTL desktop interface, product and order imports, duplicate prevention, stock ledger, returns, kits, commissions, reporting and role-ready user structure through my specialist software team. The system can be designed around exact decimal calculations, immutable invoices, audit logs, company-owned hosting and secure handling of ZATCA signing keys, with backups and a restored-copy safeguard against live invoice issuance. My Excel and database experience is especially relevant to reliable voucher, price-list and Salla export processing. I would be glad to deliver this as a clearly scoped, practical system with source code and ownership kept in your company accounts. Choose me to coordinate the implementation and turn these detailed operational and ZATCA requirements into a dependable WMS.

User Avatar
Flag of UNITED KINGDOM

Your first release needs one dependable stock record for two Salla stores, manual sales, and ERP vouchers, while ensuring every issued B2C document satisfies ZATCA Phase 2 rules. I would separate Excel ingestion from the domain layer, using idempotent source identifiers for orders and vouchers, an immutable stock ledger, and exact-decimal VAT calculations. A modular backend with PostgreSQL is well suited to ledger integrity, audit trails, queued ZATCA reporting, encrypted signing-key access, and restore-safe environments; an Arabic RTL web interface can support desktop barcode workflows. Delivery would follow your milestones: validate imports and stock cards first, then simulation-tested UBL 2.1 signing, QR, hash chain and credit notes, followed by commissions, reports, deployment notes and the parallel run. I would test duplicate imports, kits, returns, discount and fee totals, and recovery boundaries before handover. I cannot claim unverified prior ZATCA or Salla deliveries. Regards, MISS -

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅