Pith. sign in

REVIEW 4 major objections 5 minor 23 references

Smartphone-Based Food Traceability System Using NoSQL Database

T0 review · 4 major / 5 minor · reviewed 2026-08-07 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗

Pith's one-line read The paper claims a smartphone-based traceability system using RFID and phone sensors can track perishable food through the supply chain, and that its MongoDB-based server responds faster than MySQL as sensor data volume grows.

desk verdict A plausible incremental engineering report whose central performance claim rests on an under-specified, one-paragraph benchmark; worth reading for the cost model and system description, but not yet enough evidence to accept the efficiency conclusions. read the letter →

arxiv 2506.02033 v1 pith:GQ7ZKDDA submitted 2025-05-30 cs.OH cs.CY

Muhammad Syafrudin , Ganjar Alfian , Norma Latif Fitriyani This is my paper
classification cs.OHcs.CY
keywords foodtraceabilitysmartphone-basedsensingRFIDNoSQLdatabaseMongoDBperishablesupplychaintemperatureandhumiditymonitoringkimchi
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

This paper tries to establish that an inexpensive, smartphone-based traceability system can keep perishable food safe by tracking where it has been and what temperatures and humidity it experienced, and that this design is faster than traditional alternatives as data grows. A phone-connected RFID reader logs each kimchi box's electronic product code at production, transport, and distribution, while phone-attached sensors record temperature, humidity, and GPS. The authors report that the MongoDB-based NoSQL server responds faster than the MySQL-based SQL server when sensor data volume and client counts increase, and that the RFID handheld reader responds faster than a QR code reader. If these results hold, traceability becomes affordable enough for smaller suppliers and gives consumers verifiable cold-chain history. The paper's own limitations section acknowledges that scalability, regional deployment, stakeholder cooperation, and technical failures remain practical concerns.

What carries the argument

The load-bearing pieces are the EPCIS event store, the RFID reader chain, and the sensor-data repository. The Arete Pop dongle reads passive EPC Gen2 tags and sends the electronic product code through a custom Android app to a web service; the EPCIS database, following the GS1 standard, records what, where, when, and why for each product movement. The Smart Temp Checker FTC-001 attaches to a phone to log temperature and humidity, with GPS coming from the phone itself. On the server, an embedding-based MongoDB repository stores each sensor document as a device ID, a timestamp, and a sub-document of readings, whereas the SQL design splits DeviceInfo and sensorData into two joined tables; the paper claims MongoDB's schema-less, horizontally scalable design yields faster writes and reads under load.

What would settle it

Run the same write benchmark with fixed data volumes (for example, 10,000, 100,000, and 1,000,000 sensor records) and fixed client counts, replicating MongoDB 3.6 versus MySQL 5.7 on the same hardware; if MySQL's response time is equal or lower at any realistic kimchi-data volume, the paper's central performance claim is contradicted. Similarly, repeated timing of the Arete Pop RFID reader versus a QR code reader at 10 cm and 20 cm, with reported means and standard deviations, would settle the device response-time claim.

Watch

Extended reading notes

Core claim

The paper's central claim is that a smartphone-based food traceability system combining an RFID handheld reader with temperature, humidity, and GPS sensors can track perishable products through the supply chain, and that this design is more efficient than traditional methods as data volume grows. In the kimchi supply chain, each box carries a passive EPC Gen2 RFID tag; staff at production, transport, and distribution read the tag with a phone-connected reader, while phone-attached sensors log environmental conditions. The paper reports that the NoSQL MongoDB repository responds faster than MySQL when storing increasing volumes of sensor data and that the RFID reader answers faster than a QR code reader at 10 cm and 20 cm reading distances. These results are presented as evidence that the system offers accurate traceability with improved efficiency.

Load-bearing premise

The reported speed advantage of MongoDB over MySQL and RFID over QR rests on a test setup the paper does not fully describe: the data volumes, number of clients, repetitions, and error margins are not given, so the comparison cannot be reproduced or safely generalized.

Editorial extensions

If this is right

  • A perishable-food producer could deploy the system for roughly $200 per RFID reader plus $100 to $300 per phone and $20 to $30 per sensor, making traceability affordable for smaller supply chains.
  • If MongoDB's embedding-based sensor repository is as efficient as reported, the same design can absorb growing sensor streams without schema migrations.
  • If the RFID reader's response-time advantage holds, warehouses can scan more boxes per minute with a handheld dongle than with a QR code reader.
  • Consumers and managers would receive a complete product history, including electronic product code, time, location, temperature, and humidity, allowing verification of cold-chain integrity at any point.
  • Under peak loads, such as harvest or promotion periods, the horizontal-scaling design of MongoDB could keep response times stable where a relational database might bottleneck.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • Because the paper reports only qualitative performance trends with no error bars, the decisive test of its central claim is a controlled benchmark; until that benchmark is published, the MongoDB-versus-MySQL advantage should be read as a hypothesis rather than an established result.
  • The same hardware and data schema could be tested in other perishable supply chains, such as fresh fish or dairy, where temperature and humidity excursions are more frequent; the system's value would then hinge on whether real-world trip data, not simulated loads, still favor the NoSQL repository.
  • The cost figures suggest the system could be deployed with consumer-grade phones, but the paper leaves open whether stakeholders would accept the privacy and data-sharing trade-offs; a field trial with cooperative producers and distributors would test adoption, not just performance.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

4 major / 5 minor

Summary. The paper proposes a smartphone-based food traceability system (FTS) for perishable food, demonstrated in the kimchi supply chain. The system combines a smartphone-connected RFID handheld reader, smartphone temperature/humidity and GPS sensors, an EPCIS-based tracking layer, and a NoSQL MongoDB repository for sensor data. The central claims are that the proposed system improves efficiency in handling large volumes of sensor data and that the RFID reader outperforms a QR code reader in response time, based on the measurements summarized in Section 3.1 and Figure 5. The paper also provides a cost analysis of the hardware and discusses trade-offs between NoSQL and relational databases. The main evidence for the efficiency claim is a brief simulation description with no benchmark protocol, no numeric results, and no error bars.

Significance. If the efficiency claims are substantiated, the described system would be a practical low-cost traceability option for cold-chain food supply chains, with concrete hardware choices (Arete Pop RFID reader, Smart Temp Checker FTC-001, passive EPC Gen2 tags), cloud-server integration, and a cost estimate in Section 3.3. The authors also give credit for building on prior work, particularly the embedded-document MongoDB design of references [10] and [20], and for openly discussing operational limitations in Section 3.4. However, the paper's central comparative performance claims are not yet reproducible: Section 3.1 omits data volumes, concurrent-client counts, numbers of repeated measurements, database configuration details, and statistical dispersion measures. Moreover, the MongoDB-versus-MySQL comparison is confounded with a schema-design difference, and the Conclusion's scalability statement directly conflicts with the limitations discussion in Section 3.4. The novelty relative to the authors' earlier publications is also not clearly delineated. The paper's value is therefore conditional on a substantial strengthening of the empirical evaluation and a clearer contribution statement.

major comments (4)
  1. [Section 3.1, Figure 5] The central performance claims—MongoDB responds faster than MySQL as sensor-data volume grows, and RFID reads faster than QR codes—are supported only by qualitative trend descriptions. The text identifies the server and client hardware but does not report the data volumes tested, the number of concurrent clients, the number of repeated measurements, the exact read/write operations timed, or the database configurations (indexes, storage engine, journaling, isolation level). Without this information the curves in Figure 5 cannot be reproduced, and the abstract's general efficiency claim is not supported. Please provide a complete benchmark protocol, numeric results, and error bars or confidence intervals.
  2. [Section 3.1 and Figure 3] The MongoDB-versus-MySQL comparison is not apples-to-apples because the two repositories differ in schema design as well as database engine: Figure 3(a) uses an embedded-document schema per sensor event (attributed to reference [10]), while Figure 3(b) uses a normalized two-table schema with a foreign key. Any observed latency difference could be due to document-versus-relational modeling, indexing, or write patterns rather than to MongoDB versus MySQL as engines. The paper should control these factors or explicitly disentangle engine-level from schema-level effects, and should report whether statistical tests show the differences are meaningful.
  3. [Section 4 versus Section 3.4] The Conclusion states that the system 'demonstrates substantial scalability' and processes data 'more efficiently' as the volume of sensor data and the number of objects increase, but Section 3.4 identifies scalability in larger supply chains as a primary concern and notes that if the system lacks adequate scalability it 'may struggle to maintain performance and reliability.' These statements need to be reconciled: either the scalability claim should be qualified to the tested range, or evidence should be provided that the system scales beyond the simulation shown in Figure 5.
  4. [Sections 1, 2.2, and 3.1] Large parts of the system architecture, including the smartphone-based monitoring concept, the embedded-document MongoDB repository, and the overall EPCIS-based traceability approach, appear to be carried over from prior publications by the authors (references [5], [10], [20], and [22]). The current paper says it 'confirms' the embedding approach rather than independently evaluating it. The contribution list in Section 1 should therefore explicitly state which system components are new in this study, and the experimental validation should target those new components rather than reusing previously published design choices without a comparison baseline.
minor comments (5)
  1. [Section 2.1] The phrase 'as can illustrated' should be 'as can be illustrated,' and in Section 2.2 the sentence 'Fig. 2(a) and 2(b) illustrates' should use the plural verb 'illustrate.'
  2. [Section 3.1] The statement that 'average response times were recorded from multiple readings' does not report the number of readings or the dispersion of those readings; please specify N and the variance or standard deviation for each point in Figure 5.
  3. [Figure 5] The text does not describe the axis labels, units, or error-bar convention used in Figure 5; please add these details and state explicitly whether the plotted points are means, medians, or representative runs.
  4. [Reference [10]] Reference [10] appears to omit the article title and journal name in the formatted entry; please correct the bibliographic entry.
  5. [Section 2.1] EPCIS is a GS1 standard for sharing event data rather than a database itself; the manuscript should clarify how the EPCIS repository is implemented and how it relates to the separate sensor database discussed in Section 2.2.

Circularity Check

0 steps flagged · score 0.0 of 10

No significant circularity: the central efficiency claim rests on new measurements in Figure 5, while the cited prior work supplies architecture and schema choices rather than the predicted result; the under-reported benchmark setup is a reproducibility concern, not a circularity.

full rationale

The paper's central performance claim—that the MongoDB-based server responds faster than MySQL and that the RFID handheld reader is faster than QR—is supported by the empirical comparisons in Section 3.1 and Figure 5, described as measured 'average response times' recorded from 'multiple readings.' Nothing in the paper defines server response time or device response time in terms of the claimed outcome, and no parameter is fitted to a subset of the data and then renamed as a prediction. The NoSQL embedding schema is attributed to Kang et al. [20] and the SQL schema to the authors' earlier work [10]; these citations transfer design precedent, but the reported latencies are measured in the present study rather than imported from those references. The sentence 'The current study confirms that this embedding approach is well-suited for managing extensive sensor data repositories' is a broad confirmation without a detailed derivation, but it does not reduce the later MongoDB-vs-MySQL result to the citation: the measured comparison is logically independent of the cited design choice. The absence of reported data volumes, concurrent-client counts, number of repeated measurements, and error bars for Figure 5 is a serious reproducibility limitation and weakens the strength of the efficiency claim, but insufficient experimental detail is not circularity. Therefore no circular step can be exhibited, and the appropriate score is 0.

Assumptions & free parameters 1 free parameters · 2 assumptions · 0 invented entities

No mathematical derivations are present, so there are no fitted constants in the usual sense. The free parameter listed captures the under-specified simulation setup that the performance claims depend on. The axioms are background assumptions from standards and prior publications that the paper adopts without independent testing.

free parameters (1)
  • Simulation data volume and client count = not reported
    The server response time comparison in Fig. 5(b) depends on the amount of sensor data generated and the number of concurrent clients, but these values are not stated, so the results cannot be reproduced or assessed.
assumptions (2)
  • domain assumption The EPCIS database follows the GS1 standard for supply chain data exchange.
    Section 2.1 states this without evidence; it is a background standard assumption.
  • domain assumption The embedding scheme for MongoDB sensor documents (from Kang et al., 2016) is well-suited for raw sensor data.
    Section 2.2 'confirms' this scheme based on prior work [20], but provides no comparative evaluation.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Smartphone-Based Food Traceability System Using NoSQL Database." pith.science (2026). https://pith.science/paper/GQ7ZKDDA

@misc{pith2026250602033,
  author       = {Pith},
  title        = {Pith review of: Smartphone-Based Food Traceability System Using NoSQL Database},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/GQ7ZKDDA}},
  note         = {Machine review of arXiv:2506.02033}
}
read the original abstract

With growing consumer health awareness, ensuring food safety and quality throughout the supply chain is crucial, particularly for perishable goods. Contamination can occur during production, processing, or distribution, making real-time monitoring essential. This study proposes an affordable Smartphone-based food traceability system (FTS) that utilizes RFID technology and smartphone sensors. A smartphone-based RFID reader tracks products, while integrated sensors monitor temperature, humidity, and location during storage and transport. The system is assessed in the kimchi supply chain in Korea, providing real-time data to both managers and consumers. It offered comprehensive product tracking, including temperature and humidity records, ensuring transparency and safety. Compared to traditional methods, the proposed system demonstrated improved efficiency in handling large volumes of data while maintaining accurate traceability. The results highlight its potential for enhancing food safety and quality across supply chains.

Figures

Figures reproduced from arXiv: 2506.02033 by the authors.

Figure 1
Figure 1. Architecture of smartphone-based food traceability system (FTS). [PITH_FULL_IMAGE:figures/full_fig_p003_1.png] view at source ↗
Figure 2
Figure 2. Implementation of smartphone-based FTS: (a) handheld reader and (b) sensors. [PITH_FULL_IMAGE:figures/full_fig_p003_2.png] view at source ↗
Figure 3
Figure 3. An illustration of (a) a Smartphone-based generated sensor record in a NoSQL (MongoDB version 3.6) and [PITH_FULL_IMAGE:figures/full_fig_p004_3.png] view at source ↗
Figures from the paper (2 more)
Figure 4
Figure 4. Figure 4: The webpage interface of smartphone-based FTS: (a) gathered sensor data and (b) product history. [PITH_FULL_IMAGE:figures/full_fig_p004_4.png]
Figure 5
Figure 5. Figure 5: Performance analysis of smartphone-based FTS: (a) device and (b) server response time under different [PITH_FULL_IMAGE:figures/full_fig_p005_5.png]

Discussion (0). Sign in to comment.

Reference graph

Works this paper leans on

23 extracted references · 19 canonical work pages

  1. [20]

    Kang, I.-H

    Y .-S. Kang, I.-H. Park, J. Rhee, and Y .-H. Lee MongoDB-Based Repository Design for IoT-Generated RFID/Sensor Big Data IEEE Sensors J., vol. 16, no. 2, pp. 485–497, Jan. 2016, doi: 10.1109/JSEN.2015.2483499

    arXiv 2016

  2. [10]

    Alfian, M

    G. Alfian, M. Syafrudin, and J. Rhee Real-Time Monitoring System Using Smartphone-Based Sensors and NoSQL Database for Perishable Supply Chain Sustainability, vol. 9, no. 11, p. 2073, Nov. 2017, doi: 10.3390/su9112073

    work page doi:10.3390/su9112073 2017

  3. [5]

    Alfian et al

    G. Alfian et al. Improving efficiency of RFID-based traceability system for perishable food by utilizing IoT sensors and machine learning model Food Control, vol. 110, p. 107016, Apr. 2020, doi: 10.1016/j.foodcont.2019.107016

    work page arXiv 2020

  4. [22]

    Syafrudin, N

    M. Syafrudin, N. Fitriyani, D. Li, G. Alfian, J. Rhee, and Y .-S. Kang An Open Source-Based Real-Time Data Processing Architecture Framework for Manufacturing Sustainability Sustainability, vol. 9, no. 11, p. 2139, Nov. 2017, doi: 10.3390/su9112139

    work page doi:10.3390/su9112139 2017

  5. [1]

    Trienekens and P

    J. Trienekens and P. Zuurbier Quality and safety standards in the food industry, developments and challenges Inter- national Journal of Production Economics, vol. 113, no. 1, pp. 107–122, May 2008, doi: 10.1016/j.ijpe.2007.02.050

    work page doi:10.1016/j.ijpe.2007.02.050 2008

  6. [2]

    Regattieri, M

    A. Regattieri, M. Gamberi, and R. Manzini Traceability of food products: General framework and experimental evidence Journal of Food Engineering, vol. 81, no. 2, pp. 347–356, Jul. 2007, doi: 10.1016/j.jfoodeng.2006.10.032

    work page doi:10.1016/j.jfoodeng.2006.10.032 2007

  7. [3]

    M. M. Aung and Y . S. Chang Traceability in a food supply chain: Safety and quality perspectives Food Control, vol. 39, pp. 172–184, May 2014, doi: 10.1016/j.foodcont.2013.11.007

    work page doi:10.1016/j.foodcont.2013.11.007 2014

  8. [4]

    L. Wang, S. K. Kwok, and W. H. Ip A radio frequency identification and sensor-based system for the transportation of food Journal of Food Engineering, vol. 101, no. 1, pp. 120–129, Nov. 2010, doi: 10.1016/j.jfoodeng.2010.06.020

    work page doi:10.1016/j.jfoodeng.2010.06.020 2010

Show all 23 references
  1. [6]

    Abad et al

    E. Abad et al. RFID smart tag for traceability and cold chain monitoring of foods: Demonstration in an inter- continental fresh fish logistic chain Journal of Food Engineering, vol. 93, no. 4, pp. 394–399, Aug. 2009, doi: 10.1016/j.jfoodeng.2009.02.004

    2009 doi

  2. [7]

    Bouzembrak, M

    Y . Bouzembrak, M. Klüche, A. Gavai, and H. J. P. Marvin Internet of Things in food safety: Literature re- view and a bibliometric analysis Trends in Food Science & Technology, vol. 94, pp. 54–64, Dec. 2019, doi: 10.1016/j.tifs.2019.11.002. 7 A PREPRINT - J UNE 4, 2025

    2019 doi

  3. [8]

    M. M. Aung and Y . S. Chang Temperature management for the quality assurance of a perishable food supply chain Food Control, vol. 40, pp. 198–207, Jun. 2014, doi: 10.1016/j.foodcont.2013.11.016

    2014 doi

  4. [9]

    Thakur and E

    M. Thakur and E. Forås EPCIS based online temperature monitoring and traceability in a cold meat chain Computers and Electronics in Agriculture, vol. 117, pp. 22–30, Sep. 2015, doi: 10.1016/j.compag.2015.07.006

    2015 doi

  5. [11]

    Aloi et al

    G. Aloi et al. Enabling IoT interoperability through opportunistic smartphone-based mobile gateways Journal of Network and Computer Applications, vol. 81, pp. 74–84, Mar. 2017, doi: 10.1016/j.jnca.2016.10.013

    2017 doi

  6. [12]

    Sharma, J

    S. Sharma, J. Raval, and B. Jagyasi Mobile sensing for agriculture activities detection in 2013 IEEE Global Humanitarian Technology Conference (GHTC), San Jose, CA, USA: IEEE, Oct. 2013, pp. 337–342. doi: 10.1109/GHTC.2013.6713707

    2013

  7. [13]

    Rajak, A

    P. Rajak, A. Ganguly, S. Adhikary, and S. Bhattacharya Internet of Things and smart sensors in agricul- ture: Scopes and challenges Journal of Agriculture and Food Research, vol. 14, p. 100776, Dec. 2023, doi: 10.1016/j.jafr.2023.100776

    2023

  8. [14]

    Sathiya, K

    V . Sathiya, K. Nagalakshmi, K. Raju, and R. Lavanya Tracking perishable foods in the supply chain using chain of things technology Sci Rep, vol. 14, no. 1, p. 21621, Sep. 2024, doi: 10.1038/s41598-024-72617-3

    2024 doi

  9. [15]

    K. Lin, D. Chavalarias, M. Panahi, T. Yeh, K. Takimoto, and M. Mizoguchi Mobile-based traceability system for sustainable food supply networks Nat Food, vol. 1, no. 11, pp. 673–679, Nov. 2020, doi: 10.1038/s43016-020- 00163-y

    2020 doi

  10. [16]

    J. Ahn, H. Gaza, J. Lee, H. Kim, and J. Byun Oliot EPCIS: An open-source EPCIS 2.0 system for supply chain transparency SoftwareX, vol. 23, p. 101477, Jul. 2023, doi: 10.1016/j.softx.2023.101477

    2023

  11. [17]

    H. L. Gaza and J. Byun tracES++: Applying Incremental Computation to Temporal Information Diffusion Analysis for Online Object Traceability IEEE Access, vol. 12, pp. 78811–78824, 2024, doi: 10.1109/ACCESS.2024.3394543

    2024

  12. [18]

    EPC C-1 G-2 / ISO 18000-6C RFID IC,

    “EPC C-1 G-2 / ISO 18000-6C RFID IC,” EPC C-1 G-2 / ISO 18000-6C RFID IC. Accessed: Aug. 13, 2024. [Online] Available: https://www.emmicroelectronic.com/sites/default/files/products/datasheets/4124-ds.pdf

    2024

  13. [21]

    Denshine® FTLAB FTC-001 SmartLab Smart Temperature Humidity Checker (Blue),

    “Denshine® FTLAB FTC-001 SmartLab Smart Temperature Humidity Checker (Blue),” Denshine ® FT- LAB FTC-001 SmartLab Smart Temperature Humidity Checker (Blue). Accessed: Aug. 26, 2024. [Online]. Available: https://web.archive.org/web/20240902090016/https://www.amazon.ca/Denshine%...

    2024

  14. [23]

    S. A. Ajila and D. Wu Empirical study of the effects of open source adoption on software development economics Journal of Systems and Software, vol. 80, no. 9, pp. 1517–1529, Sep. 2007, doi: 10.1016/j.jss.2007.01.011

    2007 doi

  15. [24]

    Ven and J

    K. Ven and J. Verelst The Organizational Adoption of Open Source Server Software by Belgian Organizations in Open Source Systems, vol. 203, E. Damiani, B. Fitzgerald, W. Scacchi, M. Scotto, and G. Succi, Eds., in IFIP International Federation for Information Processing, vol. 2...

    2006 doi

Pith tools

Reviewed August 7, 2026 · model on record in the stance chip above.